Send private message

You must be logged in to send a private message.


No friends yet.

Group membership


  • mklog replied on the discussion topic Problem with files/photos on elgg update from 1.8 to 2.3
    Wow, I'm experiencing very rare behavior. I tested the migration process in a new clean virtual machine and I've been upgrading version by version. In this machine Ubuntu Server 14+Apache2+PHP 5.4 everything works ok. When I copied the... view reply
  • mklog replied on the discussion topic Problem with files/photos on elgg update from 1.8 to 2.3
    First thanks for your detailed answer. Then yes, I've run the process during the upgrade but I think now that some failed because in the "upgrades" section in administration view there is a pair of links: "Comments Upgrade"... view reply
  • mklog added a new discussion topic Problem with files/photos on elgg update from 1.8 to 2.3 in the group Elgg Technical Support
    Hi guys, recently I just updated a very old elgg installation from 1.8 to 2.3, following step by step and minor version by minor version I ended the process and everything seems to work fine but "files" or "photos" not. The...
    • @dragonjon I'm not sure I fully understand your issue. What I get is that you have a problem with download files previously uploaded on Elgg 2.1 after upgrading to Elgg 2.2. While it works to download files that were uploaded on Elgg 2.2 the problem is only with the older files, right?

      Is that the (only) problem you are referring to? You mentioned "something did not work in step 2.1.3 to 2.2.0" and I'm not sure you are referring to the file download issue or mean something else went wrong.

      The information in the docs about changes in the Elgg API regarding file download should be irrelevant to you in case with the bundled Files plugin as the changes have been made in the code of the new Elgg releases already. Only in case you use a plugin (that also includes theme plugins) that overrides the Elgg core functionality it might be necessary to update the code of these plugin(s). But I don't think this is the cause for your problem either because you say that the new files can be downloaded (it would be rather a fully working or not working at all issue if the code would be in need to be updated). Anyway, Elgg 2.2 - 2.3 should be backward compatible still, so you would get a deprecation warning in the logs rather than a failure in download.

      Possible way to fix the issue (if the download issue is the only issue you are referring to to have since upgrading to Elgg 2.2) could be to upgrade to the latest Elgg 2.3. There have been bugfixes since then and maybe one of the fixes addressed the issue you are referring to. If the issue would still be unresolved on the latest 2.3.4 then it would be time to open an issue about it at github as then it might be a bug in Elgg indeed.

    • Hi @iionly, sorry for not replying before I did the whole update process ending in 2.3.4 as you recommended but the problem of downloading files was not solved. But reviewing the database and how I imagined a value of a field of each file is different in old files and new ones.
      Specifically in the metadata table, in the name_id column and the value of that name_id in the metastring table is filestore :: dir_root my old and new files had different value_id that in the metastring table corresponded to different route values ​​inside the server.
      To solve this, I have changed in the metadata table all the values ​​of value_id that corresponded to the name_id with the value of the metastring table with the same id = filestore :: dir_root, for the value_id that the new files had.
      Just like it was a recklessness but with a bit of analysis I was able to solve the problem and I'll be able to start upgrading my production version to more modern versions of Elgg.

      I think the problem came by following the instructions to duplicate the installation for development, since there is a part that I think made that modification is the part that says:
      Change the filestore data directory with an SQL string
      I'm not sure if updating version directly into the production version without having to do a server address change in the database causes the same problem, I hope not.

      Thank you very much for helping me in this matter.


    • If the path to the data directory is not the same on the development server and production server you would need to update the filestore entry in the database as described in the "duplicate site" instructions.