Since the update for Vantage Premium, we can no longer use Jetpack as it prevents access to the appearance>customise area.
If you literally deactivate Jetpack, all is fine. I have rolled back to the previous versions of Jetpack and the issue still occurs. What has been updated in Vantage Premium to cause this?
The problem here is that there is functionality built into Jetpack that is used throughout the website, and I am quite frustrated that it no longer works!
Given that both Vantage Premium updated in the last 24 hours and so did Jetpack, can someone please explain what is going on?
I have also posted to WordPress expressing the same issue.
Just to add, since the premium update, Site Info Links no longer work. Grrr
We also have several plugin-related problems as well since the last update. It is annoying. Our Content Views and Recent Post Extended plugins/widgets are not working
Hi Version Daily
We’ll continue helping you on the thread you created – Thread: Content Views plugin and Recent Posts Widget Extended plugin are not working after Vantage Premium update. Alex created this thread for his Jetpack/Vantage related issues, so we’d like to keep his thread on topic :)
Hi Alex
Sorry to hear about the hassle. We’ll run some Jetpack tests now and get back to you. Can you perhaps send through a link to where we can see your Site Info links not working, we’re not quite following you there. Thanks.
I’ve answered in more detail below Andrew.
Hi Alex
The most recent update of Vantage was a fairly substantial one. Sorry to hear you’re having issues with it. We added support for Jetpack’s new site logo feature. This is the only Jetpack related change we’ve made. We did some fairly extensive testing, but maybe there’s one situation that we missed.
Do you by any chance have access to your PHP error logs? If so, can you try get the error message that’s causing the error? In the meantime, we’ll do some investigating on our side.
I’ve looked at the access logs that I can extract from the hosting interface as that details every activity. However I cannot see anything relating to the message I got – I should have screen shot it really. There are no error logs at present either so I cannot provide much more information I’m afraid.
Hi Andrew,
the site info links is the part where you enter the copyright information. in the bottom of the footer. I have followed your instructions precisely from documentation and other support threads to add the link (using html mark up) in the copyright text. This worked before the update, but not now. I would love to give you a web link to see it in action, but the website is not quite complete and has not gone public yet. My client would not be best pleased… It’s only a few days away so I can wait until then if necessary (the site information link is not a big issue, but I would like the link back to my own site in the coming weeks!) Please advise. If I need to send the link by email to support, also let me know.
Thanks
Hey Greg,
I also went through the typical deactivating plugins to find out if there were conflicts – when removing Jetpack all was fine. I also checked the updated version of Jetpack for debugging just to be on the safe side.
Upon doing this I identified that there were issues with the W3 Total cache plugin (which I have had installed since the inception of the website and before use of the Vantage template), that could potentially cause problems with Jetpack. Upon removing the W3 plugin and reinstalling the updated version of Jetpack, there were no more conflicts and I could access the appearance>customise screen, On this basis, it would appear that the conflict was with the caching plugin. I am now using WP Fastest Cache which is working well and hasn’t yet presented any conflicts with either the theme or Jetpack updates.
At this point, I am now curious why W3 Total cache was ok before the updates? I updated Jetpack a good few hours before the theme update and had no problems accessing any areas of the backend. Yet as soon as I updated the theme, it went a bit haywire. I also had to re-enter the product key after updating which was slightly odd, but naturally I made sure all setting were as they were previously.
Crucially, I now have Jetpack back up and running which is operating in all areas as it should be. The only issue I have now is the site information link problem.
Apologies Alex, the Site Information Text field is now stripping all HTML, that’s new, I’ll log ticket with the guys now.
Braam just let me know it’s been fixed. We’ll push an update in the next couple of weeks I expect.
Hi Alex. We're just doing some testing on this update. We'll be pushing it out later today. Keep an eye out for 2.3.1.