PHP error generated by a front-end button in Helix Ultimate - Forum | JoomShaper
Solved Helix Framework

PHP error generated by a front-end button in Helix Ultimate

Asked by Allen 1 year ago Last activity 1 year ago

I recently installed a new Blog extension, RSBlog! by RS Joomla. Each blog post has a button allowing printing, PDF creation, and subscribing for all guests. For designated users, I am able to provide additional editing capability after login. A post example is at https://www.certifiedinfosec.com/resources/blog/1-myth-the-board-and-c-suite-have-no-role-in-cybersecurity.

The post's actions available to all public users (guests) from the button's drop-down actions work just fine. However, attempting to use the edit action available from the button drop-down for authorized editors results in a 500 error PHP exception that traces back to Joomshaper Helix Ultimate:

Your site caused a blank screen upon a visit of this URL:


https://www.certifiedinfosec.com/resources/blog?view=form&layout=edit&p_id=10&return=aHR0cHM6Ly93d3cuY2VydGlmaWVkaW5mb3NlYy5jb20vcmVzb3VyY2VzL2Jsb2c=

HTTP_REFERER: https://www.certifiedinfosec.com/resources/blog

Error message data:
500: Call to undefined method Joomla\CMS\Object\CMSObject::getButtonName() in file .../public_html/plugins/system/helixultimate/overrides/layouts/joomla/editors/buttons/button.php:19

LastQuery:

SELECT *, template AS name
FROM #__template_styles
WHERE client_id = 0


Full PHP error details and login credentials are in Hidden Content. Please advise.

Accepted answer

Marked as the solution
Atick Eashrak Shuvo Staff

Hello Allen,

Sorry for the inconvenience this issue is causing. Could you please check again now and let me know if the problem is resolved on your end?

Looking forward to your response.

Best regards

2 more replies

Allen Asked this

Yes, it is resolved.

Is this a custom fix that I need to be aware of for future updates to Helix Ultimate, or is this a bug that will be addressed in the next template update?

Atick Eashrak Shuvo Staff

Hello Allen,

Sorry for the inconvenience. We're aware of a minor bug and a fix will be included in an upcoming update.

Please marked the issue as solved

Log in to reply.