Support Forum
I just discovered this error, when trying to load the Widgets in the Admin dashboard:
Error thrown
Call to undefined function sp_abort_display_forum()
The error goes away and widgets admin loads properly when Template Tags SP plugin is deactivated. Re-activating the SP Template Tags and Widgets plugin causes the error again and inability to manage widgets.
We had configured a template tag to show recent forum posts in a sidebar widget. That widget does still render recent forum activity as expected. But I am unable to edit any widgets with Template Tags plugin activated. By deactivating Template Tags I can access the widgets Admin, but am unable to edit the forums widget.
I was last able to manage widgets 3± weeks ago.
We are using a child theme of Reboot 2.3.0, and I do not recall seeing any recent notification(s) about necessary template modifications required. Please advise if I missed any changes required for my child theme.
SimplePress Version: 6.6.3 Build: 15872
SimplePress Theme Framework: Reboot 2.3.0
WordPress Version: 5.8.1
Wordpress Theme Framework: GeneratePress Version 3.0.4
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Does SimplePress provide support in these forums anymore?
This error persists when viewing Widgets admin when SP Template tags plugin activated:
Error thrown
Call to undefined function sp_abort_display_forum()
Anyone else experiencing this?
Hello...???
@spsupport
@spcommunitysupport
@elindydotcom
@mr-papa
@yellow-swordfish
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Looks like you posted in the Community forum which isn't monitored. It's usually for user-to-user help. As a platinum user you can post the Gold/Platinum forums or open a private support ticket.
Let me know if you'd like me to open a support ticket for you or if you prefer to get this thread moved to the gold/platinum support forum.
Thanks.
SP Community Support said
Let me know if you'd like me to open a support ticket for you or if you prefer to get this thread moved to the gold/platinum support forum.
Oops! Sorry...
Please move to support forum or advise if I should start new topic.
Thanks @spcommunitysupport !
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Hi:
We haven't made any changes in the past three weeks. Was WP Upgraded in the last three weeks? If so, do you remember what the older version was vs the current version?
Are you able to push the site to a staging domain? Curious is you switch out the theme if the issue goes away (maybe there was a minor update to GP that caused an issue).
Also, when the error occurs, I bet there's a message in the debug.log file. Can you post that message?
Thanks.
Simple Press said
I bet there's a message in the debug.log file...
Nothing related to widgets or SP is getting written to debug.log.
I did find a bunch of the following in WP error_log, but nothing when actually replicating the widgets.php error...
[31-Oct-2021 09:18:10 America/Denver] PHP Warning - preg_replace(): Compilation failed: (*VERB) not recognized or malformed at offset 9 - file: /forum-plugins/search/template-tags/sp-search-template-functions.php - line: 104 - function: preg_replace
Staging site is currently out of commission. Switching themes to troubleshoot this is not an option at this time. This may have been going on for months for all I know, to be honest. There was a GeneratePress 3.1 update within the past few weeks, with the changelog found here.
Sorry to make this hard on you, but it is not of major urgency here. If you're unable to replicate the issue, further troubleshooting on my part will have to wait, as we're migrating servers and have a major overhaul in the not too distant future.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Yeah, that's not much to go on. Without anything useful in the error log we'll need to log into the site and directly troubleshoot on it. But that means we'll need the staging site because we'll be disabling everything else to make sure it's not a conflict before we start modifying our code to add debugging stuff in it...
Simple Press said
...that's not much to go on.
I understand. If the issue cannot be replicated and there are no other reports, we clearly have a specific conflict going on, and resolving it will have to wait as this is not a critical matter. I merely wanted to report it here in case others were also encountering the error.
Thanks for the response.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
Thanks for the report. I'm happy to help dig into it whenever you're ready. Sometimes, like you said, there might be an ongoing issue but because folks don't see it, it doesn't get reported. So I'm definitely interested in troubleshooting this. I just don't want to do it on your live site knowing that we'd likely have to change code to get to the root issue if it's not a conflict.
Simple Press said
...there might be an ongoing issue
Roger that. I wouldn't be surprised considering our config and plugin mix.
I neglected to mention this is a legacy WPMU installation with SP installed on the primary site of the multisite network.
FYI: The issue is resolved by activating the WordPress Classic Widgets plugin, reverting the Widgets admin to it's previous state. The error most likely started occurring after Blocks were integrated into widget management, with a fairly recent WP update.
Simple:Press powers the Tripawds Discussion Forums.
It's better to hop on three legs than to limp on four.
The Tripawds Blogs Community is made possible by The Tripawds Foundation.
1 Guest(s)