Molongui
Forum Replies Created
-
Thank you so much for your detailed feedback and willingness to assist with troubleshooting!
We’ve successfully reproduced the issue on our test environment and have identified a solution. We’re set to release an update (version 4.9.2) tomorrow. Please update the plugin once it’s available and verify if the issue is resolved on your end as well.
We sincerely appreciate your longstanding support of our Molongui Authorship plugin over the past 4 years. Your satisfaction is our priority, and we’re glad to hear it has been working well for you.
If everything is working smoothly after the update, we kindly ask you to consider sharing your positive experience by leaving a 5-star review. Your feedback means a lot to us!
Could you please let us know once you’ve updated and checked if the issue is resolved? We’re here to assist further if needed.
- This reply was modified 1 year, 10 months ago by Molongui.
Hi @janoubie,
Thanks for bringing this to our attention! We’ll try to reproduce the issue on our testing server. Meanwhile, could you please let us know what makes you think it is that metabox the one causing conflict? It actually does nothing, just showing you information about that other plugin. Have you tried preventing the “Authors” metabox or the “Author Box” metabox (both added by our plugin) to be added to the edit post screen?
If you wish to try (that would be very helpful for us), you can prevent the “Contributors” metabox from showing adding this filter:
add_filter( 'authorship/add_contributors_widget', '__return_false' );You can disable the other two mentioned metaboxes in a similar way:
add_filter( 'authorship/add_authors_widget', '__return_false' );
add_filter( 'authorship/add_author_box_widget', '__return_false' );Which AI provider are you using? And when you click on one of the suggested tags, do you get any error on your browser console?
I know you downgraded the plugin, but if you could update it again just for making these tests, that would be very helpful.
Please let us know.
Hi @paywall,
Yes, that change was implemented in version 4.9.0. However, based on feedback like yours, we’ve reverted it. Starting with version 4.9.2, which will be released this Wednesday, you no longer need to enter an email address when adding a new guest author from within a post. Note that email addresses are still required for WordPress users.
Hope this helps!
Best regards,
Hi Maria,
Thanks for bringing this to our attention. We have been able to identify and fix the issue. We have just released a new update (4.9.1) with the fix. Please update the plugin, clear any cache you may have and check if the issue is gone. If it is not, please re-open this ticket and we will look into it.
Dear @beardev,
Thank you for taking the time to share your feedback. We genuinely appreciate your insights and apologize for any inconvenience you’ve experienced.
We’ve just released a new update (4.9.0) addressing performance issues, particularly for sites with large user bases. We’ve optimized queries and implemented improvements to ensure smoother functionality, even with extensive user lists.
Could you please check if the latest update resolves the issues you’ve encountered on your site? We’re eager to ensure that our plugin meets your expectations and delivers the performance you need.
Your feedback is invaluable to us, so please don’t hesitate to reach out if you have any further comments or suggestions. You can also contact us directly by opening a support ticket.
Once again, thank you for bringing this to our attention, and we’re here to assist further if needed.
If you find the issue has been resolved, we kindly ask you to consider modifying your review and rating to reflect your updated experience.
Best regards,
The Molongui Support Team
As we haven’t heard back from you in more than a week, we are closing this ticket now. Hopefully you have figured out how to fix the issue. If you didn’t, feel free to re-open this ticket and we will be happy to assist you.
Thanks!
Hi @minhthang1605,
If you deactivate our plugin, does the author name get displayed on that spot you mention? I mean, does your theme display the post byline (author name) by default? Most themes display them, but some doesn’t by default. You may need to look into your themes’ settings page searching for an option to make your post bylines get displayed. If your theme doesn’t provide that feature, you may want to upgrade our plugin to the Pro version so you can make use of the
[molongui_byline]shortcode. It will display the author name for the current post. Check this support article for further information.If having our plugin disabled, post bylines are displayed, please let us know so we can look into it.
As we haven’t heard back from you in more than a week, we are closing this ticket now. Hopefully you have figured out how to fix the issue. If you didn’t, feel free to re-open this ticket and we will be happy to assist you.
Thanks!
Thanks @digitalmediafbm2021 for providing access and letting us find the cause of the reported issue. It turns out it was wrong meta data causing it. The posts throwing those PHP errors were imported from another CMS and related postmeta entries were empty, causing our code to throw those warnings.
We have applied a patch to avoid missing required meta data to throw any warning, but, as explained, you should edit those imported posts and reassign authors for them.
We are closing this ticket now. If anything, please feel free to open another ticket and we will be happy to help!
Don’t worry, we will find the issue. But for that we need to know what is causing it. The URL you shared is not showing any errors that I can see. I see the plugin is running, but no error on the pages I’ve checked.
And the screenshot is not very helpful, as it doesn’t provide any information about which line of code is causing the fatal error. Could you please share your error log with us? If you cannot identify the lines you need to share, you can share the whole log using wetransfer or any other sharing service.
Could you also provide some more detail about where and when the error happens? I mean, is it happening on your Dashboard or public site? Does it happen on a particular screen or after you try to perform any action?
Please let us know so we can look into it.
Do you have a staging site? Would it be possible to have admin access to that site? I’d say it may have something to do with a plugin conflict and we need to debug it. If you are willing to share access, could you please open a support ticket here?
Could you tell which URL in your site is throwing those warnings? And is there a way we can get to see the full content of your posts?
Please let us know.
Hi @goodereader,
Could you tell which URL in your site is throwing those warnings?
Hi @kimomalcolmx,
Thank you for your feedback, and we’re sorry to hear that you’re experiencing issues with the plugin after the last WordPress update (do you mean WP 6.4.3?). We strive to ensure our plugin works seamlessly with all updates, so it’s concerning to hear about these critical issues.
To better assist you and resolve the problem, could you please provide more details about the errors you’re encountering? This will help us pinpoint the issue and work on a solution promptly. Additionally, for faster support, feel free to reach out to our dedicated support team by opening a support ticket here or here. We’re here to help!
Looking forward to hearing from you soon so we can get everything sorted out.
Hi @alefnula,
Thanks for reaching out! Yes, that was introduced as a security measure to avoid any unprivileged author publishing content in the name of others. Latest release (4.7.10) includes a hook so you can bypass that constraint. Just add this snippet to the Custom PHP option in the Authors > Settings > Advanced screen (or any other place you prefer, like in your child theme’s
functions.phpfile):add_filter( 'authorship/post_as_other_author', '__return_true' );That should do it!