Plugin Author
StaxWP
(@staxwp)
Hi, can we setup a staging site so we can test?
Settings normally migrate once you updated.
Please re-run the migration by accessing the admin area with a parameter:
/wp-admin/?stax-v-update-20
so it should look like this:
example.com/wp-admin/?stax-v-update-20
This won’t give any notification but it will run under the hood the migration again.
The original settings are kept so nothing is lost.
Please let me know
I already spent hours fixing them all by hand, thanks a lot. You guys obviously did not test this before releasing the new update. I see there is another user that had the same issue and none of your suggestions worked.
Hi. The migration is working, however some users encountered this issue. We are not yet sure what caused this, because so far nobody has provided any logs. It could be anything… like server memory limit. We didn’t expect this to happen and we didn’t do it on purpose either.
We’ll be pushing a backwards compatibility today that will make use of the old saved data, so users with migration issues can still use the plugin.
I’m sorry for the inconvenience.
Plugin Author
StaxWP
(@staxwp)
Hi, starting with version 2.1.3, we added safe fallback for older settings from v1.
Old settings are now being taken into consideration and are available in the Widget settings. You can switch to the new settings if you like or just leave them as they are.
This makes the migration from v 1.x safe. No settings were lost while you updated to v2.
You can safely update to v2.1.3 and previous settings will take place. Old settings will show in the Stax Visibility tab when editing an Elementor widget or section.
Thanks for your patience and support and our team is always here for you.
All the best
Gabriel
Plugin Author
StaxWP
(@staxwp)
Hi, let me know if you tested the latest version and everything works as it should.
Not only do your suggestions not work. I cannot create logic for new sections now, the rules are just ignored.
Hi. What rules did you apply? Can you post some printscreens? Thanks
latest update not working for me either.
i apply rule to show / not show for logged in users and it ignores it.
wp fusion seems a better way to do it at present
>latest update not working for me either.
>i apply rule to show / not show for logged in users and it ignores it.
>wp fusion seems a better way to do it at present
Yes, this is also what I did, the new version seems to be totally broken now.
Maybe it works ok for new installs? But not if you upgrade.
Plugin Author
StaxWP
(@staxwp)
We will check the logged in/ not logged in condition but with the latest version all settings are backwards compatible.
Thanks
Hi,
The option is working. Make sure your Show/Hide option in the General tab is set to “Show”. That means the widget will be shown only when the conditions are met.
Here is a small demo: https://kapwi.ng/c/fTJUtAYy
You are incorrect on both counts. Settings are NOT moved over and the option is not working. If you give me an email I will send you credentials to access to my site so you can see for yourself.
Plugin Author
StaxWP
(@staxwp)
Hi, If you have the latest version, v2.1.3, you no longer need to migrate or move the settings since old ones are kept and if available are displayed in the editor settings. Forums policy here doesn’t allow to share credentials unfortunately. Maybe you can export a page and share it on pastebin.com to check the contents.
Thanks
Facts:
1. Upgraded to v2.1.3 and lost all my settings.
2. Features are not working now.
3. Other people are having the same issues.
Looking at screen shots will not resolve this, you need to debug the issues.
You don’t have an support email?
As I said, I will gladly provide credentials for my website to you privately so you can investigate theses issues and save other users the pain I have had to go through.
Sigh, over a week and still waiting for someone to address these issues. Compatibility does not work for me in version v2.1.3, so I have lost all my settings. Also, rules are ignored for sections now. Some controls do work, text boxes, buttons, etc. So, a workaround is to set rules for each and every control in the section.
