Plugin Contributor
Qurl
(@qurl)
After you drag a widget in, make sure you save it first before trying to change DW options for it.
Exactly my point. It used to do something, now it doesn’t and stays “dynamic” from the get go. Conditional choices are not respected frontend, even though backend has the desired setting.
Plugin Contributor
Qurl
(@qurl)
Did you change or update the theme?
My theme hasn’t changed either, so yeah, my WP environment remained static if that’s your question ;). All things equal, this issue arose somehow.
edit: thanks for coming back to me on this
-
This reply was modified 7 years, 3 months ago by
cockpitseeker. Reason: thanks to the dev
Plugin Contributor
Qurl
(@qurl)
Hmm… I have the feeling the database with the dw settings go haywire for some reason. The only change that has been made between the previous version and this one is a bugfix in the pages module. So, more or less static also.
Just to be sure, your previous version was 1.5.13?
I confirm. Haven’t skipped a beat of your previous updates.
Plugin Contributor
Qurl
(@qurl)
Let’s try this…. please do a deactivate – activate cycle of the DW plugin.
Behaviour remains the same :/
- saved widget stays dynamic with some random presets
- changing these presets isn’t taken into account frontend-wise
Is it possible a very high number of widget would cause a problem here? Like IDs assignment or something, because the one more widget I’m trying to add is the 100th…
Plugin Contributor
Qurl
(@qurl)
No, that should not make a difference. The ID field in the database table can be 11 digits long. Maybe the widget_id is extremely long, but to be honest I can’t imagine a widget_id longer then 100 chars.
It’s getting a hard nut to crack apparently. Do other things save to the database? Like options, posts, etc?
Regarding that, it seems that the settings previously used on the last tweaked widget are the ones that apply by default to new ones.
In the meantime I reverted to 1.1.13 and:
- settings now properly apply – solves the issue
- however, dynamic settings still auto apply (instead of static after saving)
- …and previously used settings are the ones applying by default also (before applying changes that now work).
I use widgets with blank (no) titles quite often if this could have a bearing on how the code changed between current v1.5.14 and former .13 version.
Plugin Contributor
Qurl
(@qurl)
The only change made between .13 and this .14 is the bugfix in the pages module. I’ll do a diff just to be sure.
Plugin Contributor
Qurl
(@qurl)
I’ve done a diff between .13 en .14. Two things have changed:
– Extra condition when retrieving the hostname (used in URL module)
– Bugfix in Pages module (which I already mentiond)
So, I’m sorry, I have no idea what’s causing your issue. But it’s hard to believe it has something to do with the upgrade to .14.
I just wanted to add that I am experiencing the same issues since updating all of my websites to version 1.5.14 (on WordPress 5.1).
I have navigation menu widgets and when I add a new one since the update, it immediately starts off as ‘Dynamic’. I go into the settings and click “Set all options to ‘No'”, then tick a page (e.g. About Us) and “all childs”. The menu appears on the homepage but not About Us or any of its child pages. If I untick ‘all childs’ it then appears on About Us as expected and not on the homepage but of course I need it to appear on the children as well.
When creating 2 new menu widgets and adding them to the relevant pages (e.g. About Us and News) the menus appear on the opposite pages (About Us menu on News and vice versa).
I have set one of my sites back to .13 and the issues do not occur. All menus appear on the correct parent and child pages.
Plugin Contributor
Qurl
(@qurl)
Looking also at the reports at the other thread, there might be an issue with the homepage because of the change being made to pages. I’m looking into that.
