- This topic has 24 replies, 2 voices, and was last updated 3 years, 4 months ago by
.
-
Posts
-
Hi,
After the update to BuddyPress 8.0 and updating Grimlock for BuddyPress, we see the following error in the browser console. I will post a screenshot soon.
We have tested this with the old version of BuddyPress and Grimlock for BuddyPress and the console is error-free.
Thanks.
This reply has been marked as private.
Hi Nifty,
Thank you for bringing this issue to our attention. However, we can’t reproduce this error with our demos.
Could you deactivate all plugins that have not been installed with your theme during its setup and all existing custom PHP code snippets please? And then, could you confirm me that the issue is still persisting please?
Please also make sure that you have the latest theme version and that all recommended plugins are up-to-date. Finally, you could also consider clearing all activated caching system as well as your browser cache before investigating any further. If you want to read more on what browser cache is and how to clear it, here is an article that might help you: How to Clear Internet Cache in Every Major Browser.
We’re waiting for your feedback.
Thank you.
Hi Manathan,
Thanks for your reply.
Certainly. We have done as requested and still see the issue. If you deactivate the BP Better Messages plugin and use the built-in BuddyPress message area to compose a message, you should see the error message(s). After deactivating the plugin, the URL to Compose a message would be, for example, /members/demo/messages/compose/
Thanks.
Hi,
Thank you for your feedback Nifty. 🙂
Unfortunately, it seems we don’t face this issue by following your steps. It’s best if we take a quick look at your website.
Could you create a new website user for us please? If possible with administrator capabilities so we can make a quick check of your settings.
You can post the user name and password in your next reply and mark it as private to keep this between us.Also, are we free to deactivate plugins for our tests? In this case, I invite you to make a backup before we investigate your website further in order to make sure you don’t loose any data if something goes wrong.
Thank you.
Hi Manathan,
Thanks for your update.
We have set up a new demo website without any changes for you to take a look at. You are welcome to deactivate plugins. Access will be provided soon in another post.
Thank you.
This reply has been marked as private.
Thank you for granting us access to your WP Admin Nifty. 🙂
We will investigate further to find from where this issue is coming from.
We will be back to you ASAP.
Thank you for your patience.
Regards,
No problem. Looking forward to hearing back. 🙂
Thanks.
Hi Nifty,
Thank you for your patience.
We investigated and we found out that this issue was related to BuddyPress, more specifically from the “legacy” part. Some scripts need to be removed to prevent this error from happening. However, it seems BuddyPress team will not plan to fix that.
Temporarily, you can install and activate BP Global Search plugin. It seems that the plugin’s authors met this error as they made some development in their plugin to prevent this.
We have to explore others solutions. however, we will be back to you as soon as we found how to solve this.
Best,
Hi Manathan,
Thanks for looking into it and the temporary fix. We really appreciate it. 🙂
We will be keen to hear back from you once a solution has been found. The issue also causes the autocomplete not to work in the Send To field and the heading of the mobile menu “Menu” does not display due to this. However, you may have already noted this.
Thank you.
Hi Nifty,
You’re welcome. 🙂
Concerning the mobile menu, we did not noticed. Can you please share a screenshot with us?
Best,
Hi Manathan, 🙂
Sure. Adding to my above post, it can also be seen that the menu actually breaks and the links appear out of where they are supposed to be and display above it.
Thanks.
Thanks for your feedback Nifty. 🙏🏼
We’ll be back to you once we found how to solve this.
Best,
Hi Manathan,
Just wondering if there’s any updates on this? 🙂
Thanks.
Hi Nifty,
Sorry, it seems we didn’t come back to you.
Can you confirm me you’re referring to the menu please? This issue should be solved. On our end, all is working fine. Can you please make sure all is up to date and that this issue still appearing? In that case, I suggest you to create a new topic as it might need some investigations and this topic is related to an issue due to the “legacy” part of BuddyPress.
We’re waiting for your feedback. 🙂
Best,
Hi Manathan,
The issue isn’t resolved from what we can see. When a user composes a message, the error message still comes up in the browser console (as per the screenshot with our original post). This error message goes away when the Grimlock for BuddyPress plugin is deactivated, though.
We’ve tried the suggested workaround of using the BuddyPress Global Search plugin, but consequently, this causes the autocomplete function of the “Send To” field to stop working when a user is composing a message.
Thanks.
Hi Nifty, 🙂
In my previous answer, I was referring to the menu.
Concerning the error in the browser console when composing a message, it is not fixed yet. However, no release date can be disclosed as we have a lot to work on. As we told you, this issue was related to BuddyPress, more specifically from the “legacy” part. Some scripts need to be removed to prevent this error from appearing. However, it seems BuddyPress team isn’t planing to fix that.
The best solution is to install and activate BP Global Search plugin. I understand that this plugin create another issue. However, in case it is blocking you, we suggest you to reach the plugin authors. They might have a quick solution that we don’t know of.
To go further, we invite you to post your request on their support forums: buddypress.org/support
Best,
Hi Manathan,
Thanks for your response and ongoing help. 🙂
We’re not sure what you mean by it being an issue related to the “legacy” part of BuddyPress as other sites we run with BuddyPress (regardless of the template or site theme being used), don’t have error messages in the browser console. We only see the error on sites which have Grimlock activated. The first screenshot we posted also includes a reference to Grimlock for BuddyPress within the browser console error. We’re just trying to get a better understanding of how this issue is related to the “legacy” part of BuddyPress. 🙂
Thanks.
Hi Nifty,
You’re welcome. 🙂
To be more precise, the Grimlock for BuddyPress JS crashes because of this error related to the “Legacy” part of BuddyPress. That is why the error you get is related to Grimlock for BuddyPress. In other words: This error happens in Grimlock for BuddyPress due to an issue in the “Legacy” part of BuddyPress. However, our plugin is not the only one to suffer form this issue.
BP Global Search has the same problem, but they made this fix themselves in their plugin. That’s why when BP Global Search fixes this issue when it is installed. Note that BP Better Message should also fix this issue, as it overloads the BP messaging system.
Hope this will help you better understand this issue. However, let me know if you need more explanations.
Best,
Hi Manathan,
Thank you for clarifying further. 🙂
You’re welcome. 🙂
Hi Nifty,
We’re glad to inform you that we have just released a new update of Grimlock fro BuddyPress. Updating this plugin to the latest version should fix this issue. 🙂
However, in case this issue persists, can you please come back to us?
After the update, the problem should now be fixed. However, you might still be seeing the issue because your browser cache is showing you an older version of the page (browsers do that to load pages faster). To see that the issue is resolved you will need to empty your browser cache and reload the page. If you want to read more on what browser cache is and how to clear it, here is an article that might help you: How to Clear Internet Cache in Every Major Browser.
Kindest regards,
Hi Manathan,
Thank you very much; the latest update appears to have fixed this issue. 🙂
Thanks.
I’m glad to read that Nifty! 🙂
Best,
The topic ‘Errors when composing messages’ is closed to new replies.
