atomizer

i did as you suggested using the custom code
thanks

the site runs on a shared server, so i guess that’s considered a virtual server
and yes, they do run LightSpeed

i can out the line as you suggested, but then i assume the next update will re-add it… and i’m sure i’ll forget about it ??

the other major item i forgot to mention is adding the missing ability to organize content in the media gallery by user-defined folders from the UI

i wonder if the latter issue – page change notice before editing a page – might not have something to do with revisions?

i have not yet been able to reproduce it reliably, but i’ll keep a check on it

thanks

i’m also seeing the following 2 notices when i simply go to edit a static page, before actually editing it…

Quick Cache: detected changes. Found cache file(s) for the designated “Home Page” (auto-purging).

Quick Cache: detected changes. Found cache file(s) for the designated “Posts Page” (auto-purging).

hi Raam – thanks for the reply

regarding the Home and Posts page cache clearing, the static page i was working was not new – only updated – and no links in any menu would have changed

i also see that QC is detecting changes to the Posts and Home pages whenever a static page is updated…

Quick Cache: detected changes. Found cache file(s) for the designated “Posts Page” (auto-purging).

Quick Cache: detected changes. Found cache file(s) for the designated “Home Page” (auto-purging).

it is absolutely expected that what the WP author wrote is precisely what is rendered on the visitor screen.

anything else constitutes a bug.

translating content back to the default lang, and using a 3rd party to do it, when that content is available in its original form in the db, is, as prometheangroup says, a waste of resources and one which can produce unwanted results

i would also wonder why flash is being utilized, even when the language is default

got it – thanks

then i don’t understand the purpose of “apply to content” – is that simply an on/off switch where, if unchecked, it means nothing will be lazy loaded?

that’s the problem though – if i disable it for content, it doesn’t work for images, iframes

is there any debugging i can do to help you out?

rob, after asking several times WHY you are using google to “translate” content back to the default language instead of using the db content, i got no answer — that is what frustrated me

at any rate, you admit there’s a bug and therefore the plugin is broken, is it not?

regardless of whether google is supposed to do the job or not, i think wp authors would prefer having their original content put back from the db, unless you are certain that google has an exact, non-cached copy of the text strings when the user reverts back (and maybe google does since it translated the def lang) — still seems a bit sketchy to me though

on second thought, what if the connection to google explodes when the translation back to default is done?

seems like it is best to pull from the db, period

I agree 100% on this, and in some cases this actually might be the case, where Google does not translate to their version of default language, but instead they translate to your original language.

i think you’re missing my point — the point is, GLT should have control over setting the strings back to the default language, NOT goole

from the statement i quoted, and from the appended strings which should not be appended, it seems clear that you are using google to translate back to the default lang.

why?

you should be using the db/wp cache, NOT GOOGLE!!!

i’m marking this plugin as broken

i understand what you’re saying, but i still don’t understand why you are using google to translate the default lang? when the user translates back to the default language, this should come DIRECTLY from the db or wp cache or whatever, but not from google

it seems to me that GLT should be aware of what the default language is and then set the link for the button/flag/list item appropriately, where appropriately means pulling the text strings from the db and not google

thanks for the reply, but i still don’t understand why google is being used at all to “translate” the default language – this should come straight from the db, should it not?