Jeroen Maathuis
Forum Replies Created
-
Forum: Plugins
In reply to: [BuddyPress Members Only] Site CRASHI’ve exactly the same issue. the file /rules/shortcoderestriction.php is indeed missing.
For now I temporarily solved it by commenting out line 44 in /buddypress-members-only.php:
//require_once("rules/shortcoderestriction.php"); // 2.8.5
So far I did not experience other issues with commenting out this line.After a long search I finally found a solution:
- Go to an post / page editor screen.
- Cick the Q-button of Qubely in the top right corner.
- Duplicate the active preset (3 dot menu > Duplicate). I didn’t configure anything at that new preset. I just duplicated it.
- Activate the newly created preset (3 dots button > Activate).
After this the issue was gone at my website. ??
Thanks to jgarib at the Themeum Qubely Github repository: https://github.com/themeum/qubely/issues/33#issuecomment-688462935
- This reply was modified 4 years ago by Jeroen Maathuis.
I have exactly the same issue as topicstarter @stewarthowell on my testing environment since I updated several plugins including Qubely. To bad I didn’t pay attention after updating wich plugin exactly it went wrong.
Tried to use the CSS in the header of by files. Updating Apache / PHP / MariaDB is to difficult to perform now and everything else than Qubely is just working fine.
It is very frustrating as I can’t updat emy production website right now. ??
I’ve disabled many plugins that have something to do with any markup of the website but nothing helps. Aaargh…Forum: Fixing WordPress
In reply to: Convert to regular block no longer working – WP 5.6 GutenburgI also experience the issue that my reusable blocks can not be converted to regular blocks. The button indeed does nothing. Most of my resuable blocks use “Gutenberg post blocks” by wpxpo.
However I found out that when I click the “Edit” button of the resuable block and then click “Save” without making any modifications to the title of the resuable block I AM able to click the “Concert to regular block” to make it really a regular block again.
I can confirm the update fixed the issue. ????
- This reply was modified 4 years, 3 months ago by Jeroen Maathuis.
I don’t have any clue on how to do this on the Neve theme. Can you help me out?
Forum: Plugins
In reply to: [WooCommerce] DB Error after update@m155y5 I have exactly the same issue. The report seems to include filepaths which I don’t want to expose here in public. I was wondering whether I can send you the report in private.
Another thing I discovered is that there is a placceholder all the time on top of the WooCommerce admin pages. Like there is a message loading but never appearing.
- This reply was modified 4 years, 6 months ago by Jeroen Maathuis.
Eventually I discovered more dashboard pages were affected (like the menu editor) and as above error shows the source seemed to be at the CBX Changelog plugin. I have contacted the developer of the CBX Changelog plugin and he also wasn’t able to reproduce it.
I digged some further in the issues and found out that other PC’s and browsers at my house didn’t have the issue too.
I ended up in clearng all cookies and website data for the affected WordPress websites and that did the trick! It is now working normal again. ??- This reply was modified 4 years, 7 months ago by Jeroen Maathuis.
I found out that the above mentioned div-element should get filled by Javascript.
After looking around with the DOM Inspector of Firefox an error in the developper console got my attention:Uncaught Error: Syntax error, unrecognized expression: https://domainname.tld/wp-admin/admin.php?page=wc-settings&tab=advanced jQuery 10 <anonymous> https://domainname.tld/wp-content/plugins/cbxchangelog/assets/js/cbxchangelog-setting.js?ver=1.0.7:31 jQuery 4 load-scripts.php:2:12681 jQuery 10 <anoniem> https://domainname.tld/wp-content/plugins/cbxchangelog/assets/js/cbxchangelog-setting.js?ver=1.0.7:31 jQuery 4
Which is caused somewhere in /wp-admin/load-scripts.php. The error refers to the CBX Changelog plugin. Deactivating that plugin solves the issue. Activating CBX Changelog again re-introduces the issue again. Strangely that plugin isn’t causing any issues on another website and it didn’t cause any issues before at the involved website.