danbailan

Hi,

I guess that I have not asked the question correctly.

After extensive testing (plug-ins turned on and off in all combinations), talking to my server people, maxCDN, I keep coming back to here.

If CDN caching is turned on with W3TC, then the site will not load. Turn it off, the site loads.

I have currently turn off all plugin-ins on my dev site except for W3TC and I have the CDN caching on – it does not load. https://dev.explorekohchang.com/

In my live site, I have all plug-ins on, W3TC on but CDN caching off io it is useable.

I would really appreciate any help you might be able to give, I know I am not a developer so my language is perhaps poor but I have followed as many protocols as possible before reaching out to you.

Hi,

I apolosgise for the delay.

You also need the graphene neo mobile helper plug-in and graphene shortcodes plug-in.

I have not pm’ed you yet as my dev site is playing up after a database update. You could therefore only test things on the live site.

Many thanks

Exactly that one, yes.

It uses shortcodes to deliver different content to respective devices.

I use a child theme with graphene theme as my base. They use/recommend this plug-in for their theme.

As I said before, collapse-o-matic has worked perfectly with this and all my plug-ins for 2 years+.

Many thanks for looking into this.

Hi,

Thank you for getting back to me.

An example of the shortcode used is

[expand title="Show Koh Mak Map" trigpos="below" swaptitle="Hide"  tag="h3"  trigclass="kohmak_beaches"]
<div style="text-align:center;margin-left:auto; margin-right:auto;margin-top: 5px;">
<img src='/wp-content/gallery/koh-mak-island-map/koh-mak-map.jpg' alt='koh-mak-island-map' class='ngg-singlepic ngg-center' style='width:100%;'/>
</div>
[/expand]

This on page https://explorekohchang.com/koh-mak/ if opened on mobile devices.

Graphene uses any mobile switcher plug in to target mobile devices with [mobile-exclude], [/mobile-exclude] & [mobile only], [/mobile-only]

As i said, this has worked like a dream for two years. I wondered if something had changed in the default collapse settings in the update, or I had something set which has gone, which I am not remembering or noticing?

Dan

Hi Bojan,

I will test as you say, starting back the other way on the plugins and report back.

Many thanks

dan

Thanks Cais,

I tried the featured image with W3TC off – no joy.

Yes, I can go through a conflict check but I think it easier to just use the WordPress option. As I said before, the only thing that’s changed is the upgrade and to have to de-activate another plug-in ( when I have everything set up and working) to counter the conflict caused by the upgrade seems a bit back to front?

Thanks

Ok. I’ll leave things as are. It took a lot of trial and error to get the minify working ;).

Thanks for your help.

Hi Cais,

It worked for the last year until I did the upgrade this morning. I have not specifically tried anything yet to troubleshoot. Something has caused the conflict in 2.1.0 as I was up to date before.

I can get round it by using the wordpress featured image but…

I have tried the featured image with each radio button setting in different combinations but always the same error as per my first post.

There is no setting in gallery settings or options that I need to change?

Thanks

Hi Cais,

Thanks for the tip – it prompted me to look at W3 total cache where I minify much of the photocrati js files. De-activating the minify js, purging the cache and then tried again, it worked in chrome.

I then re-activated the minify js in W3 Total cache, purged the cache again and it still works in Chrome. Actually much faster to load the next image than in firefox. So that’s solved. Thank you

Question on that – Do I still need to minify the photocrati js (all files embed before body). Historically, I did this because of google page analysis where there was so much from photocrati being loaded.

I have a feeling you have looked at this over there, so maybe I no longer need to the minifying using using W3 total cache?

Thanks

Hi Bas, table sent as requested to email [email protected]
Many thanks

Hi Bas,

Removed table in phpMyAdmin, back to WP admin, updated from 1.37 to 3.03. Update ok (using wp update button in plugins page), then activate. This triggers fatal error “unable to activate”. Retry activate, it works but only about 20% of buttons come through if that (80). I have a lot (370+)!

Very wary of trying the new migrate button (it says all over it be wary!) in case this loses my fallback of 1.37 database table completely. I have reverted back to that again now.

Thanks

Hi Bas,

Can you please confirm that I must delete the table called ‘wp_maxbuttonsv3’ which was created on the first unsuccessful attempt at updating to 3.02 before I attempt to try this update from 1.37 to 3.02 again?

Many thanks

I have gone back to the old plug-in for now and got the buttons back – the two different entries are there in the database. Maybe I will try a new update when it is released – at least I know I have a fallback position by reverting to 1.37. But I do like to be up to date…

Many thanks and I still love the plug-in, it’s great for affiliate deeplinks in my case, very useful and easy to use..

To be clear on the last post, the new button’s id is numerically in sequence but physically it is shown in the middle rather than at the bottom as it should be.

I have two problems it seems.

1) After the update, I initially had no buttons. I followed advice here and ended up with about 10% only of my previous buttons. I have tried several times to activate and deactivate but with the same result – it’s lot of work that has gone awol.

2) I recreated a new button but then noticed that this is not added to the list of the existing buttons at the bottom i.e as the next id in sequence but randomly somewhere in the middle.

If I go back to the old plug-in will I get all of my old buttons back? or since I have started with the new database as discussed above, will this have now overwritten the old one.

many thanks