Gustavo Bordoni

Problem resolved on 0.9.1

Hi, @jeroenrotty,

The “Liquid Web” menu has been completely removed on version 6.16.2 that went out about 45 minutes ago.

The feedback on how unexpected this looked has landed with us. A new top-level item appearing after an update can read very differently than intended, so we completely removed it.

Hey everyone, @jeroenrotty, @kipi, @stevefry77, @jsm116, @koobm, @reeeeeeeee, @puntoman, @luckisaskill, @beneppard, @senator94,

The “Liquid Web” menu has been removed. 6.16.1 went out today taking it off the sidebar, and a follow-up release (6.12.2) finished the cleanup. Our preference is for settings, licenses, and product info to live inside the plugin’s own menu, and that is the direction we are moving.

The feedback on how unexpected this looked has landed with us. A new top-level item appearing after an update can read very differently than intended, and pulling the menu is our response. The team was heads down on shipping 6.16.1, reviewing where this menu was registered across our other plugins (which is what @koobm flagged in the Kadence Blocks forum).

Thanks to everyone who wrote in.

@jeroenrotty @kipi Thank you for the feedback on this, those are really good points.

There is no need for the language around this wasn’t so aggressive.

Our team is considering bringing it to a better spot in the menu and give options to change it’s behavior.

Our goal with that was to create an experience for our Products that would enable you to see it all in a consolidated view with the features highlighted.

@kipi we are actually doing this to enable us to increase the number of free features.

• This reply was modified 3 weeks, 4 days ago by Gustavo Bordoni.
• This reply was modified 3 weeks, 4 days ago by Gustavo Bordoni.

Hi @kanky00,

I’m sorry to hear that this update created this situation, and I wanted to share some context behind the message you saw. This version contained an update to an internal library which was not compatible with older versions of Event Tickets. One complication with updates that are not compatible with older versions is that WordPress doesn’t have a great way to communicate version dependencies prior to running the updates (when auto-updates are enabled). In order to avoid a potential fatal error or other negative side effects that could arise from running incompatible plugin versions, we soft-deactivate one of the plugins and display this message instead.

To prevent issues like this from happening in the future, we do recommend keeping auto-updates disabled. This gives the site admin the chance to test updates on a staging site first to ensure that everything is working as expected with the new version. There is always the chance that the code changed in the new version may not work the same way with third party themes and plugins as the previous version did, in addition to compatibility issues that could arise with older versions of our other plugins if those plugins are not also automatically updated at the same time.

With that being said, I realize that this functionality created a difficult situation for you, which is not our intent. We found the support ticket you submitted in our inbox and will follow up with you there to help get this resolved as quickly as possible and avoid this happening again in the future.

Best Regards,

Hi @modemlooper,

I wanted to know where are you seeing this be ran all the time? The way we coded this it was meant to only show when someone has Angie installed, and if you are seeing it without using Angie its a bug.

Please share some screenshots of where you are seeing it, and I will make sure that it doesn’t on our next release.

As a side note, our MCP is not actually any code that is running in your WordPress install, it uses the REST API that comes default on WordPress, so there isn’t a way to disable it unless you remove the REST API.

Best Regards,

Hi @prove74 I would love to know what error exactly you are getting, maybe its something I can fix easily. But I would need you to look at your log file.

There is a good article on how you can get access to those here:
https://kinsta.com/knowledgebase/wordpress-error-log/

Let me know, I have a version in the making that might solve your issue but I wanted to be 100% certain before I push it out.