After update Module RokSprocket from version 2.1.14 to 2.1.15, the backend of the module was broken!
With the error warning
"Catchable fatal error: Object of class JFormFieldRL_List could not be converted to string in
... \components\com_roksprocket\fields\list.php"
I managed to fix it by myself:
in row 56 change
$this->$this->getInput()
to
$this->getInput()
Could anybody confirm that this is a general bug or only a problem on my system?
Newest joomla version 3.6.4 is running.
Do you have Advanced Module Manager installed? We have found that there is a clash with this extension. If you disable that then roksprocket works fine.
Please would you post your URL, superuser id and pswd in the secure tab of your post and i'll have a look for you.
Regards, Mark.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
This message contains only secure information that is visible to MrT, moderators and administrators
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
you hit the mark
- I have indeed installad the Advanced Module Manager! After disabling, RokSprocket works fine.
But in version 2.1.14 it already worked fine in combination with Advanced Module Manager ...
Thank you for your offer, but it concerns a sort of intranet Joomla system, so I can't give you URL etc. But never mind - my bugfix works fine for the moment and I hope that in future version of RokSprocket and / or Advanced Module Manager this will be fixed.
Ok. We're still looking into this and your suggested bugfix too. But the reason we changed RS to 2.1.15 was to fix an issue with JCE editor. Now with 2.1.15 it seems we now have an issue with AMM instead. So, we don't want to regress back... hence why we are still investigating...
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.
Ok we've looked at your suggested fix and it's absolutely correct - so thank you very much for helping us with that one... We have tested this now and are currently releasing Roksprocket 2.1.16 containing that fix - it should be available in the next 15 mins.
Regards, Mark.
Please search forums before posting. Please make sure your post includes the version of the CMS you are using and a link to the problem. Annotations on screenshots can also be helpful to explain problems/goals. Please use the "secure" tab for confidential information.