All Site Activity

  • Abdulaziz replied on the discussion topic Error when logging into upgrade.php
    I followed the steps in detail Also, the site after the transfer process appears normally, but when you do the upgrade.php lines, the site turns into this shape. I also entered my account and logged in. I think this indicates that the database... view reply
  • iionly replied on the discussion topic Error when logging into upgrade.php
    Elgg can't access the data directory or the cache folders within the data directory. Therefore, you get the site displayed without CSS styling etc. seemingly text only. The question is if Elgg can't access the data directory content... view reply
  • Abdulaziz replied on the discussion topic Error when logging into upgrade.php
    I would also like to ask another question, can the same method of restoring the site work with webmin view reply
  • Abdulaziz replied on the discussion topic Error when logging into upgrade.php
    Thus, the look of my site became even though I did all the steps shown in the tutorials, but when I did upgrade.php, the look of the site became like this https://ibb.co/pPffGNx https://ibb.co/WGMskgS view reply
  • Abdulaziz replied on the discussion topic Error when logging into upgrade.php
    It is not clear how to solve the problem. Please clarify the steps view reply
  • Nikolai Shcherbin replied on the discussion topic Error when logging into upgrade.php
    Check the permissions https://en.wikipedia.org/wiki/File_system_permissions#Traditional_Unix_permissions view reply
  • Abdulaziz added a new discussion topic Error when logging into upgrade.php in the group Elgg Technical Support
    After I made a transfer and when I log in to upgrade.php This message appeared and changed the look of the site without style, just words Oops... Error You must update your .htaccess file (use install/config/htaccess.dist as a guide).
    • I would also like to ask another question, can the same method of restoring the site work with webmin

    • Elgg can't access the data directory or the cache folders within the data directory. Therefore, you get the site displayed without CSS styling etc. seemingly text only.

      The question is if Elgg can't access the data directory content because the access permissions set for the files and folders on your server are not set correctly (that's what Nikolai was referring to) or if you haven't followed all instructions about how to move your site fully and correctly.

      You need to update some database entries if the paths on the filesystem to the Elgg root folder and/or the data directory are different on the new server. And starting on Elgg 3 you also need to make sure that the path set in elgg-config/settings.php for data directory is correct (if different on new server you need to change).

      Changes in .htaccess are only necessary if you had made any modifications on your own that contain path related data. If you not only moved the site to another server but thought to upgrade to an new major Elgg version at the same time though, this might problems not related to the server move and therefore not explained in the corresponding instructions. Never move and change Elgg version at the same time!

      Any administration tools on the server won't help. It's a matter to fix within the Elgg installation (database, install and data folders).

       

    • I followed the steps in detail
      Also, the site after the transfer process appears normally, but when you do the upgrade.php lines, the site turns into this shape. I also entered my account and logged in. I think this indicates that the database rules were linked correctly or what

  • Pranjal Pandey released a new version of the plugin The Wire Pro
  • Reuven replied on the discussion topic Duplicate Elgg 2.3 on new server
    Thank you very much Nikolai and iionly. I learn a lot from your answers. However, I reinstalled the site from scratch and the initial tests show that it works well. The problem with the images... view reply
  • Reuven replied on the discussion topic Duplicate Elgg 2.3 on new server
    Thank you iionly. I'm going to check this. view reply
  • iionly replied on the discussion topic Duplicate Elgg 2.3 on new server
    The difference in URL is definitely not a matter related to the configuration of your VPS server. It might be that the cache settings of Elgg ("Advanced Settings" in the admin area of your site) differ between the old site and new site... view reply
  • Reuven replied on the discussion topic Duplicate Elgg 2.3 on new server
    Thank you iionly. It is not clear to me why two identical installation have different behavior. The old sit is on a shared host the new one on a VPS.  Since I'm quite new to the VPS I suspect that I did not configure it... view reply
  • iionly replied on the discussion topic Duplicate Elgg 2.3 on new server
    Are you comparing the same kind of images on the same version of Elgg? There are filetype icons used for non-image files and image previews (thumbnails) for image files. For the first type of files the same image icon is used for every file of... view reply
  • Reuven replied on the discussion topic Duplicate Elgg 2.3 on new server
    Thank you. I think I duplicated the site correctly. The question is why Elgg creates this kind of icon... view reply
  • Nikolai Shcherbin replied on the discussion topic Duplicate Elgg 2.3 on new server
    I gave instructions on when to update Elgg: From Elgg Docs: * A backup of the live Elgg database. * A place to copy the live database. * A server suitable for installing duplicate Elgg site. During this tutorial, we will make these... view reply
  • Reuven added a new discussion topic Duplicate Elgg 2.3 on new server in the group Elgg Technical Support
    I duplicated my Elgg 2.3 site on a new VPS with the same URL. HopefullyI followed all the instructions here . The only difference between the two installations is the data file address.   Initial tests show that the new...
    • The difference in URL is definitely not a matter related to the configuration of your VPS server.

      It might be that the cache settings of Elgg ("Advanced Settings" in the admin area of your site) differ between the old site and new site and this might cause different URLs (e.g. with caching disabled or some caching options at least) the caching of the files might not be possible in the first place, so you won't get a "cache" URL.

      Apart from the caching options available on the Advanded Settings you might also want to create the symbolic link in the root folder of your Elgg installation. At least for me it never worked to let Elgg create it automatically. Nonetheless, the Advanced Settings page will tell you where the "cache" link would have to point to exactly within the data directory.

    • Thank you iionly.

      I'm going to check this.

    • Thank you very much Nikolai and iionly. I learn a lot from your answers.

      However, I reinstalled the site from scratch and the initial tests show that it works well. The problem with the images disappeared. 

      All the best.

       

  • Pranjal Pandey commented on the blog Elgg 4.0.0-beta.1 has been released
    This is the much needed update ! makes Elgg simpler and consistent , no more legacy elgg_*_*_* , I really love how everything is more consistent with object oriented approach and how the function based hooks have been removed , salute to Jeroen...
  • Nikolai Shcherbin replied on the discussion topic SMTP & File Size
    nginx.conf http { client_max_body_size 10m; }   /etc/php/7.4/cli/php.ini /etc/php/7.4/fpm/php.ini upload_max_filesize = 10M   service nginx reload service php7.4-fpm... view reply
  • neon replied on the discussion topic SMTP & File Size
    Thank you for your speedy reply. I will look in to the SMTP settings shortly. As for the file size, I'm using nginx so the .htaccess file is null and void. Nginx is set to allow 10MB uploads, PHP is set to allow 80MB, it seems to be the... view reply
  • iionly replied on the discussion topic SMTP & File Size
    There's a file named .htaccess in Elgg's install directory (the dot means the file is a hidden file so you might miss it on first glace). Within .htaccess you can adjust php variable values. For example, there's the line php_value... view reply