About: olly connelly

cheers Bruce.

I understand that. And wonder (now) why I asked the initial question, at least quite as I worded it.

Seems to me there’s a gaping performance hole here, with this issue. I mean, the vast majority of page content – unless, say, it’s a forum – is static. …

… In my case, the only dynamic component, for logged-in users, on any given page is the “Logout | Profile” div which, when clicked, calls the user’s username, and which will either redirect that user to a successful logout, else take the user to his or her profile page. It seems very silly for that little box, however functionally important, to slow down the entire page.

… So my original question may better have been, “How can I isolate that single div to be dynamic, whilst retaining the rest of the page as static and, therefore, caching? Using fragment caching, perhaps?”

You see my point? And understand my revised question?

For the record, I know that W3TC, that I am using, supports fragment caching now. Might that be the solution, effectively to isolate the single div, as dynamic?

It strikes me that caching is a science all of its own!!! And like any science, it’s a total bugger until properly understood! I appreciate any heads-up on what appears to me to be a most understated yet important topic, (for billions of sites): the art of *fragment caching*.

Thanks guys.

“Do you have full control over your server?”

Yes. Running APC too, BTW.

#hope!

Eduan, that is precisely the deal.

Mike, I’d tend to agree.

Thank you both. Due to time constraints, not ideal but I’m running with the iframe for now but will try again, taking into account the likely javascript conflict somewhere.

I’ll try to remember to add the eventual solution here.

Cheers Bruce. “Inconvenience” … well, it’s just web dev, huh!

Thank you for your help.

Cheers Bruce, and nice link so thanks for that.

After all, I’m working on a slightly different registration solution now (in case it helps anyone else with similar issues, searching for this kind of stuff) …

Am using Formidable Pro (top forms plugin) + their Registration plugin + their Captcha plugin + their MailChimp plugin to create the form and register the resulting user data in the usual way. Because mine is a Multisite install where I want users to be registered across all sites in one go, and because Formidable does not share data across domains (even with the WP User Management plugin, which otherwise is a cracking auto-sync-user-data plugin), I’m embedding the registration form (available on every page on the site) into an iFrame … this is one of those rare cases where an iFrame is a reasonable solution.

… So, along comes a visitor, to any page on any sub-domain, clicks the “Register me” link, up pops/slides in/whatever an iFrame with the registration form which pulls its content from the registration page on the main domain … *ajaxed if you like, all without leaving the current page*. The visitor registers via Formidable which inputs the data into the WP users table (while simultaneously setting up the Mailchimp user newsletter/opt-in email); the WP User Management plugin then syncs that user data across all sub-domains and s2Member recognizes the registration in the usual way.

… Hurrah! Hope that helps. Formidable is a premium plugin but great for all form requirements. It is not a substitute for s2Member.

** Let me say, I do hope that s2Member will soon be able to handle all of the above, seeing as Multisite is now such a big deal. Really s2Member (as with vast majority of plugins even if they do say Multisite compatible, is only a regular WP plugin. I know you guys are totally honest about this.)

Otherwise, re that “Math required” anti-spam measure. I worked out that it has nothing to do with s2Member but is actually a Simple:Press forums plugin option which, checked, hooks into the main WP registration. So sorry for the red herring.

Bueno. Ciao.

OK, got that, will play, tx again, Sir.

Tx Cristián,

I will work on this once the basic new site’s up and running, and if i have any joy will report back here.

“there’s a shortcode attribute for it from that attempt”

… Can you elaborate on that please? Something I might be able to play with?