Jok Iopas

Send private message

You must be logged in to send a private message.

Friends

No friends yet.

Activity

  • Jok Iopas replied on the discussion topic fatal error message for non logged in user
    @iionly  OK I saw the GitHub discussions now and I guess it makes sense now. Was afraid that it was only happening to me but although it is a known problem it looks that it is really a non issue.  view reply
  • Jok Iopas replied on the discussion topic fatal error message for non logged in user
    Forgot to say this happens  in elgg v 2.3 view reply
  • Jok Iopas added a new discussion topic fatal error message for non logged in user in the group Elgg Technical Support
    I've noticed that if a non logged in user tries to access some urls that contain the "theme_sandbox" path then in some cases there is a message displayed for a fatal error example of such...
    • I can't recognize it. Check your server logs.

    • This is a known issue. See open issues at https://github.com/Elgg/Elgg/issues?utf8=%E2%9C%93&q=is%3Aopen+sandbox+

      The theme sandbox as it is currently implemented is not ready for public use. For example, the error when trying to access the theme_sandbox/components page is caused by no user being logged in while Elgg tries to display the user icon of the "currently logged in user" on this page. The error on other pages are most likely for the same or similar reasons, i.e. Elgg trying to run an API methos on the logged-in user entity that is just not available for logged out users. The developers plugin (including the sandbox) has been written with the development phase in mind and not necessarily the "show off" use case. As the corresponding issues are still open there might be some changes made at some point. But I guess it's currently a rather low priority to work on it.

    • @iionly 

      OK I saw the GitHub discussions now and I guess it makes sense now.

      Was afraid that it was only happening to me but although it is a known problem it looks that it is really a non issue. 

  • Jok Iopas replied on the discussion topic Group discussion topics are gone after upgrade to version 2
    I have no idea why vendor/elgg/elgg/engine/lib/upgrades/2015062900-1.11.2-discussion_plugin-e28c7afa4f5f24ec.php was not executed. Like you said it is possible that I enabled the discussions plugin before running upgrade.php but I doubt it... view reply
  • Jok Iopas replied on the discussion topic Group discussion topics are gone after upgrade to version 2
    @iionly Thanks for the detailed answer. I am quite sure I followed all the instructions for the upgrade procedure as stated in this page. Now and when I go to the "Upgrade" page (corresponding menu item in the "Configure"... view reply
  • I have successfully upgraded from Elgg version 1.9 to version 2. I did a step by step upgrade , specifically : 1.9 > 1.10 then 1.10 > 1.11 then 1.11 > 1.12 and finally 1.12 to 2.0.4 In all the 1.* upgrade steps I encountered...
    • @iionly

      Thanks for the detailed answer. I am quite sure I followed all the instructions for the upgrade procedure as stated in this page. Now and when I go to the "Upgrade" page (corresponding menu item in the "Configure" section in the admin area sidebar menu) I see a  "Your installation is up to date!" message. 

      In any case I solved the problem by performing this SQL query 

      UPDATE `elgg_entities` SET `subtype` = 47 WHERE `subtype` = 13;

      In my particular case this updated the entities table and changed the entity subtype  from "groupforumtopic"  to "disucssion". I don't recommend it for anyone else as the number IDs will be different. 

      I am sure the yoursite.url/upgrade.php  script performs a similar update function, I really don't know what might have gone wrong in my case as I ran it each time I went from version to version.

      All is good now , the topics are back, so I am happy. Thanks again for answering,  you are one of the few users in this forum who provides detailed and thorough tips when it comes into solving problems. 

       

       

    • I've looked into the upgrade scripts that are included in version 2.0.4. There no async upgrades (which would have to be executed from the "Upgrade" page manually) but there's a script at vendor/elgg/elgg/engine/lib/upgrades/2015062900-1.11.2-discussion_plugin-e28c7afa4f5f24ec.php which should have run when calling yoursite.url/upgrade.php (or clicking on the "Upgrade" button on the admin dashboard).

      I don't know why it hasn't been correctly executed on your site when upgrading to 2.0.4. Could it be that you enabled the Discussions plugin before running upgrade.php? In this case there might have been a new row added to the subtype db table (for discussion subtype) and the upgrade script might not have been able to update the existing row for the groupforumtopic subtype in the subtype table.

      As you see in the upgrade script the approach is slightly different from what you have done to fix the problem on your site: instead of updating the subtype id in the entities table to match the discussion subtype's id the existing groupforumtopic subtype is changed to the discussion subtype in the subtype table instead.

      I guess if you now have already changed the id in the entities table the first db update done in the upgrade script would be no longer necessary to be executed. But as you see in the script, there are two more updates done: river entries and log table entries. The log table entries might not be that important as the log table would sooner or later get cleaned up by the logrotate plugin anyway. But I think you should fix the river table entries in any case as they would point to a non-existing view otherwise and would have the wrong subtype (groupforumtopic instead of discussion). The last part of the script would only enable the Discussions plugin. But as you have it already enabled that part is not relevant anymore.

    • I have no idea why vendor/elgg/elgg/engine/lib/upgrades/2015062900-1.11.2-discussion_plugin-e28c7afa4f5f24ec.php was not executed. Like you said it is possible that I enabled the discussions plugin before running upgrade.php but I doubt it as running upgrade.php was a routine thing to do immediately after the step by step, one version at a time,  manual updates. 

      Following your tip and looking into the code of the upgrade script  I performed this SQL query:

      UPDATE  elgg_river
      
      SET view = 'river/object/discussion/create', subtype = 'discussion'
      
      WHERE type = 'object' AND subtype = 'groupforumtopic'; 
      

      Now the activity entries relating to discussions are displayed correctly in the activity page of the site. 

      I chose not to update the log table as it did not matter much. 

      Thanks again for your help with this. 

       

       

  • Jok Iopas commented on the plugin [Elgg 1.8-1.12 & 2.X: Userpoints group widget]
    @iionly  OK thanks for this info.
  • Jok Iopas added a new discussion topic Group discussion topics with no comments monitoring in the group General Discussion
    I am looking for a plugin that will monitor group discussions that are inactive, meaning that there are no comments/replies for them. After a time period passes (eg a week or month) and no comments are made,  the group owner/admin...