davidblair6
Forum Replies Created
-
Forum: Plugins
In reply to: [Pootle Pagebuilder - WordPress Page builder] Live Edit strange behaviourG’day Jamie – I’ve sent you a screencast, the problem is reproducable 100% on the website I made the screencast with, using 18tags and PBpro/premium. I have other sites using the same combination that work ok – still trying to discover what the differences are but can’t see them. All using latest WP & plugins.
Forum: Plugins
In reply to: [Pootle Pagebuilder - WordPress Page builder] Live Edit strange behaviourI get similar things happening, also often when live editing a column in a 2-col row, as soon as you click the edit col container btn the col jumps out of its side position to down below and that then becomes a hard edit if you publish… have to edit using edit page instead.
Thanks wfasa, I’ve just updated to 6.1.4 and this has fixed the problem. Also a ton of other great updates and fixes!
So I disabled Ultimate Google Analytics and now get:
[Apr 15 21:30:53] Setting up scanRunning and starting scan
[Apr 15 21:30:53] Scan can’t continue – stored data not found after a fork. Got type: boolean
[Apr 15 21:30:53] Scan process ended after forking.OK I enabled debugging and the log now reports: (.. in place of server path)
[Apr 15 21:20:15] Setting up scanRunning and starting scan
[Apr 15 21:20:15] Scan can’t continue – stored data not found after a fork. Got type: boolean
[Apr 15 21:20:15] Use of undefined constant user_level – assumed ‘user_level’ (8) File: ../wp-content/plugins/ultimate-google-analytics/ultimate_ga.php Line: 1047
[Apr 15 21:20:15] Scan process ended after forking.
[Apr 15 21:20:15] Use of undefined constant user_level – assumed ‘user_level’ (8) File: ../wp-content/plugins/ultimate-google-analytics/ultimate_ga.php Line: 1047I just tried a re-install of WordPress, still the same completely repeatable problem:
[Apr 15 21:10:28] Analyzed 3100 files containing 36.39 MB of data so far
[Apr 15 21:10:33] Scan can’t continue – stored data not found after a fork. Got type: booleanI have the same problem