What is going on???? MODS TAKE NOTICE!!!

[effCup]

After a switch back to t=, f= urls for a couple of hours, the SEO form is now once again in operation, and this time it looks to be operating in navigable form.

[Jenny48549]

Originally Posted by effCup

After a switch back to t=, f= urls for a couple of hours, the SEO form is now once again in operation, and this time it looks to be operating in navigable form.

It appears that the vBSEO plugin is active again and the indexes are working. Thanks for your patience

[Greenman]

Can you put that in layman's terms, for us mere mortals that don't speak techno?

[Jenny48549]

Originally Posted by Greenman

Can you put that in layman's terms, for us mere mortals that don't speak techno?

The plugin that makes the Model Indexes work correctly is enabled again. If you click on a name, you should get the right model page instead of "404 Not Found". I can't say it any less "techno" than that...

[ballyhoo]

is anyone else not able to "see" their own, or other member's profile pics?
I don't mean member's avatars, but their profile pics. here's my profile;



granted, my computer is nearly as old as a Betamax player. and obviously
it could be another slight side effect of the recent system repairs.

[beutelwolf]

Originally Posted by ballyhoo

is anyone else not able to "see" their own, or other member's profile pics?
I don't mean member's avatars, but their profile pics. here's my profile;

Same issue with me.

[stagliano]

any more kvetching and the sleepover is cancelled!

[effCup]

Originally Posted by Greenman

Can you put that in layman's terms, for us mere mortals that don't speak techno?

The thread this discussion is in, its url (universal resource locator) as far as vef & vBulletin is concerned, is this:

http://vintage-erotica-forum.com/showthread.php?t=282737

Its "key", as far as the back-end database is concerned, is the thread id (number) that follows the "t=" bit above.

The "showthread.php" bit is a php (programming language) function endpoint, which accepts an input for the target thread id (the bit above that follows the question mark). It can also accept an optional page number, e.g. t=282737&page=3. That function retrieves the relevant data from the database & sends it to your browser for display.

But, the vBSEO* plugin allows that same thread to instead (also) be accessed via this "more meaningful" (to humans) url:

http://vintage-erotica-forum.com/t282737-what-is-going-on-mods-take-notice.html

* vB = vBulletin, the software package inside which vef resides.
* SEO = Search Engine Optimisation.

--------
More technical discussion:

I think the vBSEO plug-in, or at least this part of its function(s), is largely a "have", as:

a) mod. changes to thread titles are typically not reflected (updated) in these so-called "meaningful urls", so they can become quite meaningless.

b) the vBSEO plug-in offers only a very shallow implementation of RESTful design (that link takes you to a more technical discussion). The vBSEO plug-in gives the thread a name, but provides no context:

vef/t282737-what-is-going-on-mods-take-notice.html

For all we know (i.e. at face value) it could be located within:
/classic-models/classic-pornstars/
or:
/discussion-&-talk-forum/funnies/
or whatever.

A properly meaningful url for this thread would instead take something like this sort of form:

vef/info-&-help-forum/help-section/what-is-going-on-mods-take-notice.html

[Greenman]

Nope still no idea what the smeg you are on about-if that is layman's terms I hate to think what the technical bit is I think however, reading between the lines, I can work out what went wrong but I am sure others don't know either.

[beutelwolf]

Originally Posted by Greenman

Nope still no idea what the smeg you are on about-if that is layman's terms I hate to think what the technical bit is I think however, reading between the lines, I can work out what went wrong but I am sure others don't know either.

All these things you click on on VEF are URLs, addresses your browser uses to connect to the WWW. But VEF is not a static set of html pages, it is constantly changing in content. So these addresses are actually calling a little program (the things with ".php" at the end), which reads VEF content from a database and sends such a seemingly (from your browser's pov) static page back to your browser.

However, certain things are very commonly looked at, e.g. the porn star section with their newest entries. So to avoid making a program create this page afresh every single time it is requested this plugin was apparently organising the efficient re-use of those generated pages. The net effect of the whole thing (when it is working properly) is to make the site faster.

Now, I do not really know how it is organised (never worked with the software myself), but that is my take on things.