I wanted to upgrade my site from using Elgg 2.3.7 to Elgg 3.0.1.
I have no problems with Elgg 3.0.1 installation ( using composer).
Then I copied one of my plugins that works with Elgg 2.3.7 to my new Elgg 3.0.1 ( /mod/my_plugin ).
Here is the problem I have:
When I activated my plugin, I got the error message saying 'Error'. That's the entire error message I have on the page.
Then I checked my error log, it has no error there in my log/httpd/error_log file.
Does anyone has this problem with activating their own plugins on Elgg 3.0.1?
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by RaĆ¼l Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Rohit Gupta@Rohit_1990_3676
Rohit Gupta - 0 likes
- seri_ng@seri_ng
seri_ng - 0 likes
You must log in to post replies.There is a high chance that your elgg 2.x plugin will not support elgg 3.0. There has been lot of changes in the core due to which the plugin might not work.
Here's the list of changes: https://github.com/Elgg/Elgg/blob/3.0/docs/appendix/upgrade-notes/2.x-to-3.0.rst
If your plugin is developed by someone else, then you can contact the person to update your plugin and make it compatible with 3.0. Or, if you have developed the plugin then you need to make the required changes as mentioned in the link above.
Regarding the error_log, can you check phpinfo() once, just to be sure that the path for your php error_log file is correct.
Thanks Rohit. There are several Elgg core functions we used in our plugins that are now deprecated in Elgg 3.0.*. I am working on replacing those deprecated functions with newer ones.
About the error_log, now I can see my error_log by turning on the logging in mysite/admin/settings/advanced