diegocanal

Hi,

Sorry I had not checked the “Notify me of follow-up replies via email” box so I did not notice you had replied to me.

Actually I have two forms on the same page. For usability reasons I would like to change the tooltips position differently for each form –the form on the left would ideally have the tooltips being positioned to the right hand side of the fields whereas the form on the right would preferably have them positioned to the left–.

Also I would like to have control over tooltip positioning on a per viewport basis, as the two forms go from standing side by side on wider viewports to standing one below the other on the narrower viewports…so in the last scenario I would rather have the tooltips the way they are now.

Here you have the URL you asked for: https://goo.gl/SRp7Sz

Thanks!

Best Regards.

Same problem on my side. @akaydavid thanks for the tip, it worked perfectly. This bug has been around for a long long time, I hope it will be fixed sometime in the near future.

Same problem on my side. @akaydavid thanks for the tip, it worked perfectly. This bug has been around for a long long time, I hope it will be fixed sometime in the near future.

Hey @folettiwebdesigner, same behavior on my side.

The only way I’ve found to get my amp pages (posts) purged after editing and saving the original posts is to ‘Purge all caches’ —notice that ‘Purge modules’ >> ‘Page Cache: Current Page’ does not do the trick—.

• This reply was modified 8 years, 4 months ago by diegocanal.
• This reply was modified 8 years, 4 months ago by diegocanal.

Hi @cybmeta, yeah, it’s been really frustrating the lack of support and maintenance, I, too, was already considering switching to other cache solution although I didn’t take the step.

I have used W3TC for 4 years. Once I learnt how to make the most of it I started getting very good results, even for quite complex sites —Google PageSpeed Insights 100/100 on both, mobile and desktop (with the addition of 2 more plugins)—.

Unfortunately, lately, I’ve been having great concerns regarding, mainly, the security issues you’ve mentioned. The good news is that those issues have apparently been solved with the recent updates. I hope that, from now on, the plugin will remain well maintained in a timely and effective way.

I must point out that I’ve never had the need of premium support so I haven’t had to endure what allegedly many people have gone through.

Having said that, it is my obligation to say that Frederick Townes, for a long time, has provided me with a terrific plugin —I am not a programmer so I cannot tell how well coded it is, I speak purely from the end-user perspective— a free solution that has allowed me to offer a much better experience to my sites’ users and, of course, improve my business bottom line. For all that I want to show my respect for his work and say…thank you, Frederick!

• This reply was modified 8 years, 4 months ago by diegocanal.

+1

At the beginning of october 2016, along with version 0.9.5.1, a built in W3 Total Cache extensión was released to support Accelerated Mobile Pages (AMP) so now we just have to go and activate it.

Thank you for addressing the issue @tokkonopapa!

I would like to add that it is easy to solve this issue creating a new API key or regenerating the current one –many times, if it is necessary, until one is assigned without hyphens–. Nevertheless, I think this should be addressed so no one else wastes time trying to figure out why the key is not working.

Sorry, I published it twice by mistake.

@catwingz I was experiencing a similar issue and the solution was to momentaneously disable my caching plugin (w3 Total Cache) when granting permission.

@trevorsimko I was experiencing a similar issue and the solution was to momentaneously disable my caching plugin (w3 Total Cache) when granting permission.

@kfajans I was experiencing a similar issue and the solution was to momentaneously disable my caching plugin (w3 Total Cache) when granting permission.

Hi @cybmeta!

I just wanted to thank you from the bottom of my heart. Your piece of code (quick fix) works great on my side. You have saved me a lot of time and headaches.

Cheers!

I think I found where the problem was. The shortcode was using query_posts() without making a call to wp_reset_query(); –its purpose is to clean up after having employed query_posts so the original main query is restored– I just added it (to the shortcode’s file) and now the issue has gone away, without having to alter any code at all within the plugin.

It also works fine if I only add wp_reset_query(); at the beginning of oh_add_script_footer().

Of course this would confirm SOGO’s remark, although Robert might have a good point proposing to add wp_reset_postdata() and perhaps also wp_reset_query() to both, oh_add_script() and oh_add_script_footer() functions.

I hope you will excuse my lack of programming skills and knowledge, in case I am talking nonsense or saying what is obvious.

Thanks!