Search Results for 'cache'

Hello Catalin,

I was looking here in the forum on this subject since I have had problems of ouverload of CPU with the Search Live.

I tried to apply the suggested configuration in tg_ajax.php, exactly as explained, but after that it break the Next Prev ajax on the Blocks pagnation and the ajax views counter for cached pages, as reported by our colleague ieanea above.

Is there a setting that disables ajax only for Live Search?

Thank you!

I have tried adding the text suggested to the .htaccess file and clearing cache but this doesn’t work. I have also tried deactivating plugins one at a time but that doesn’t work either.

Ok thanks.
Indeed all it seems working now.
I suppose it was a cache plugin problem.
I deactivate a lot of functions and maybe it correct all this.
Regards

Hi Catalin,

I’ve done the change you mentioned, cleaned all my caches and I still can’t see the currency exchange plugin working on my website as you can see here http://take.ms/XrJ8v

It shows only the title but no currency details. That has been happening for a couple of months.

My website is https://rotadocanguru.com.br

Thanks
Rodrigo

No worries. I’ve been doing webdev since 1994, using WP since 2004, and have been managing our web servers since 1996. 🙂

So, we run a lot of high traffic news portals as well as our company B2B sites. We run WP with server side caching, and so well aware of WP behaviors. So, a ‘static’ page still has cookies loaded via PHP, and content is still added via the handler even with so-called static pages. A normal site visitor would not see an edit button. This is why you don’t see edit buttons for TIME magazine (running on WP VIP platform).

We’ve never had this issue on our sites, so I guess I was trying to give you some level of comfort there.

Personally I find injected ‘edit with pagebuilder’ buttons annoying in WP, and have always thought so — but I have this issue with all platforms going back to first version of Canvas (to date myself a little bit more).

So, to chime in – it *would* be nice to have option to remove pesky “edit this page” items when logged in for the admin user, even if via a filter hook in t he WP API.

I guess they did give you possible solution for that, so if ultra paranoid that would be the best way to go. Still, I’ve never seen a client make note of a “why is there and edit button on the photo on your home page …”

Or, put yet another technical way: proper caching plugins make a static copy of the ‘public’ DOM/render, which would be considered the rendered page with a ‘subscriber’ or ‘anonymous’ role/cookie level; not an admin level state. So, technically unless the cache method is ‘misconfigured’ — a static version of a page/post would never render with the user role/cookie state of superuser, admin, editor or author. With those user role/levels, an ‘edit’ button would not render with the DOM, and so never be part of a static page rendered and stored for public consumption.

Easily tested, by the way, through mechanisms like “fetch and render” tools like Google, Chrome Incognito mode, etc.

• This reply was modified 8 years by simchris.

if you try different cache plugins whit same results, the problems is your hosting. Switch for a better hosting company. I Use Banahosting for a site whit 2million visits per month whiout problem using Newspaper (semi dedicated plan 25USd month). If you have a little traffic like 100,000 visits per month can use a starter plan 5usd/month.

Or try another company 😛

Thanks for joining the party(I know that sounds sarcastic. But I am seriously grateful for any help). I am well aware of how it works.

But on my sites, I employ offsite caching solutions that mean I would need to be able to read cache headers on that solution which is more server time and frankly a lot more complicated than just removing the front end admin functions on WordPress.

We are about to beta and are going to start testing publicly next week if you are interested.

I don’t need a refund. I am testing out compatibility.

Proper page caching does not show conditional states in WordPress .. WP uses a session cookie to set user status and determine which micro-cached (transient) elements to show a user. So, if a cookie is set as a logged in user, then that user ‘level’ (role) would be able to see an edit button — this has been a standard in WP themes for many many years across hundred thousand themes. It is indeed considered a core ‘feature’ of WordPress.

A visitor to site without a user cookie would only see a public cached copy without any user transient extensions added to a page — just like a non-logged in user would not see the cached user bar at top of a post page, or an edit comments function, or plug-in specific functions from page builders (e.g., site origin, themify, td composer, etc.).

Welcome to WordPress!

try this, disable w3 total cache and install autoptimize, Async JavaScript (works better with autoptimize). Exclude “wp-includes/js/jquery/jquery.js” and defer other java scripts. And also minify the CSS.

• This reply was modified 8 years by aloysiuspattath.