sankari
Forum Replies Created
-
Forum: Plugins
In reply to: [Companion Auto Update] CAU 3.7.1 Fatal Error@papin Thank you from my side, too. Life provides many opportunitites for learning and as the proverb says: “Strength lies in calmness” 🙂 Keep up your good work and thanks for sharing it with the WP community.
Forum: Plugins
In reply to: [Companion Auto Update] CAU 3.7.1 Fatal ErrorAppendix:
I just observed that the dashboard is back to normal if the plugin is deactivated so it seems that the two things are related.Forum: Plugins
In reply to: [Companion Auto Update] CAU 3.7.1 Fatal ErrorAlmost the same error message here:
Uncaught Error: Call to undefined function wp_next_schedule() in /location/example.com/httpdocs/wp-content/plugins/companion-auto-update/cau_functions.php:787
Stack trace:
#0 /location/example.com/wp-content/plugins/companion-auto-update/companion-auto-update.php(294): cau_fetch_log(‘7’)
#1 /location/example.com/wp-admin/includes/template.php(1389): cau_widget(”, Array)
#2 /location/example.com/wp-admin/includes/dashboard.php(246): do_meta_boxes(Object(WP_Screen), ‘normal’, ”)
#3 /location/example.com/wp-admin/index.php(177): wp_dashboard()
#4 {main}
thrownDon’t know if this is related to it but the dashboard looks broken, i.e. not all boxes are shown (the last one is the Update Log box) and show/hide is disabled for all boxes.
Plugin version 3.7.1.
WordPress version 5.5.3Forum: Themes and Templates
In reply to: [Ample] Warnings with W3C HTML CheckerYou can add HTML5 support for scripts and styles with this function:
https://developer.wordpress.org/reference/functions/add_theme_support/#html5After this support script’s type attribute will no longer appear in the code.
Hallo again,
I found that this has nothing to do with your plugin but with the theme lacking HTML5 support. So I’m going to close this issue. Sorry for bothering you!
Hello @surbma
Thank you for your fast response. Oh, wrong address then. Sorry for bothering you!
And thank you for the hint. I am going to forward it to the theme developer.
Forum: Plugins
In reply to: [Page Builder by SiteOrigin] Conflicts with Classic Editor pluginHello Andrew
Thank you for the good news.
For Classic pages with Page Builder data in it do you consider prompting users with a notice that switching isn’t possible if they try to? I imagine that would be helpful for users and save you some support effort in the future.
- This reply was modified 7 years, 2 months ago by sankari.
Forum: Plugins
In reply to: [Page Builder by SiteOrigin] Conflicts with Classic Editor pluginHello @misplon
Thank you very much for your prompt reply and for logging these issues. Your advice in point 2 is very helpful as I was not aware of that option.
Have a peaceful day!
Forum: Plugins
In reply to: [Classic Editor] Can’t edit existing posts and pages in Block EditorHello @felipeloureirosantos
Thank you for your reply and your advice.
All those issues seem to be a result of the conflict with the Page Builder by SiteOrigin plugin. They don’t occur anymore after deactivating Page Builder.
I posted the issue in their support forum:
https://wordpress.org/support/topic/conflicts-with-classic-editor-plugin/Thanks a lot for your help so far!
Forum: Plugins
In reply to: [Classic Editor] Can’t edit existing posts and pages in Block EditorThank you very much for helping me out, @felipeloureirosantos. That’s very kind of you!
I got fives sites where it’s not working. It was really helpful that you were asking for a list of plugins: I realised that all of those sites are using the plugin “Page Builder by SiteOrigin version 2.10.5”.
After deactivating that plugin the Block Editor can be launched! So, the Classic Editor plugin seems to be conflicting with the Page Builder by SiteOrigin plugin.
For the WordPress version, the Classic Editor plugin version version and the plugin’s setting please see the initial post of this thread. I just re-checked the settings and they are correct. If you prefer to see a screenshot I can provide it to you. Just let me know.
Looking forward to reading from you 🙂
Forum: Plugins
In reply to: [Classic Editor] Can’t edit existing posts and pages in Block EditorHello @felipeloureirosantos
Thank you for replying.
I confirm that those pages/posts were made using the Classic Editor.
In the description of the plugin at https://wordpress.org/plugins/classic-editor/ it says:
When allowed, the users can choose which editor to use for each post.
On the list of posts there is a link “Edit (Block Editor)” beneath those posts, so I would expect that the Block Editor is launched.
So I have a few questions for those sites where only the Classic Editor is launched:
1) In the user’s profile the default editor is set to “Block Editor”. Why is the Classic Editor launched when creating a new post?
2) Creating a new post by specifically using the Block Editor (Posts > Create > Block Editor) brings up the Block Editor. After saving the post as draft why does it say on the post list that the post was last edited using “Classic Editor”?
2) Why can a post that has been created using the Classic Editor not be edited using the Block Editor? Does that mean that those posts cannot be edited in Block Editor as long as the Classic Editor plugin is active?
The thing is that, for posts made using the Classic Editor, on some sites the Block Editor can be launched while on others it can’t. Can you enlighten me? 🙂
Hey @nightl,
Thank you very much for sharing this information. So far I used “Custom Sidebars – Dynamic Widget Area Manager” as a workaround. It works a bit differently but did the job.
Forum: Plugins
In reply to: [Companion Auto Update] No notifications if multiple email addresses@papin Oh my, yes! Thanks for the enlightment.
Forum: Plugins
In reply to: [Companion Auto Update] No notifications if multiple email addressesPlugin version: 3.1.2
No notification received for the latest WordPress update to version 4.9.7 for all our sites with more than one email addresses. Those sites with just one email address received the notification. Could you please recheck the function? Thanks.
Forum: Plugins
In reply to: [IP Geo Block] Fatal error: Allowed memory size of [x] bytes exhausted@tokkonopapa Thanks very much for your fast response and your guidance. I increased the memory size and now the site works like a charm. It’s good we covered this issue now as a reference for those who might run into the same thing.