Group activity

  • amgad replied on the discussion topic .htaccess
    the problem solved by editing Apache server configuration in  httpd.conf by change AllowOverride None to AllowOverride All- then restart server and it's ok now ... appreciate your help  view reply
  • iionly replied on the discussion topic .htaccess
    If you haven't done it yet, call YOURSITE.URL/upgrade.php in the browser. This should flush the cache of Elgg where references to the old url might still be included. If this doesn't help, try deleting the system_cache and views_simplecache... view reply
  • amgad replied on the discussion topic .htaccess
    thanks for reply ...i did what you point to and still got the same error i looked for php mod_rewrite and it's working it put the whole site out of sub directory to the parent and still give me same error view reply
  • iionly replied on the discussion topic .htaccess
    The RewriteBase is set in the .htaccess file. If your site is not installed in a subdirectory, you wouldn't necessarily have to set the RewriteBase. But if your site is installed in a subdirectory, you have to define the RewriteBase in .htaccess... view reply
  • amgad added a new discussion topic .htaccess
    i upload my elgg 2.3 web site to the server in sub directory and update the db and elgg-config/settings.php with db user and dbname then when i go to myweb.com/test/upgrade.php in browser i got this msg " You must update your...
    • thanks for reply ...i did what you point to and still got the same error i looked for php mod_rewrite and it's working it put the whole site out of sub directory to the parent and still give me same error

    • If you haven't done it yet, call YOURSITE.URL/upgrade.php in the browser. This should flush the cache of Elgg where references to the old url might still be included. If this doesn't help, try deleting the system_cache and views_simplecache folders in the data directory to make sure that really no old cached files remain (these folders will get re-created automatically afterwards).

    • the problem solved by editing Apache server configuration in  httpd.conf by change AllowOverride None to AllowOverride All- then restart server and it's ok now ... appreciate your help 

  • Mc replied on the discussion topic Fatal error PHP error between installation step 4 and 5.
    Php 7.2 is not for production use. 7.1.11 is last stable version. I am using 7.1.8 and Elgg2.3.4 view reply
  • iionly replied on the discussion topic Removing Excess data files from webhosting account
    What your webhost is telling you is that they have a limit on the number of "inodes" for your hosting plan (shared hosting)? The number of inodes used correspond to the number of files and directories on your webspace. So, they don't... view reply
  • iionly replied on the discussion topic Fatal error PHP error between installation step 4 and 5.
    Could you try with PHP 7.1 instead of PHP 7.2? Final version of 7.2 is not yet out, and it might be that it's a bug in PHP causing this fatal error instead of just a warning as it seems to have been before. Or it might be that Elgg is just not... view reply
  • I am using elgg-1.8.19 . My webhost is telling that I have crossed the inode limit , so my account is suspended . Which excess data files from the webhost so that my account won't exceed inode limit . 
    • What your webhost is telling you is that they have a limit on the number of "inodes" for your hosting plan (shared hosting)? The number of inodes used correspond to the number of files and directories on your webspace. So, they don't limit the disc space as such but they limit the number of files you are allowed to have on your server.

      Easiest way to fix this would be to upgrade your hosting plan to get a higher limit (or no limit at all beside a disc space limit which is easier to handle in some extend as it might be a problem when hosting many large files but not when hosting a large number of small files that don't take that much disc space each). Anyway, ask your webhoster support about your options.

      The only other option would be deleting user content - file/video/audio uploads (which will also delete the files from the data directory and therefore decreasing the number of inodes used). But this is a bad choice really because your users won't like it at all and sooner or later you will have the same problem again when users have uploaded new files. The files from the Elgg install directory and mod folder can't be deleted obviously as it would make your site unuseable.

      The only other possibility would be that somewhere on your webspace countless files are created (log files?) that might be small each but a very large in number. Maybe ask your webhost about that, too. Especially, if your users haven't uploaded that many files (so it would be unlikely that these causes the exceeded inode limit).

  • Hello together, I'm new here, so thanks for the opportunity and I hope to get some help. I searched a lot but didn't find any conclusion. I'm experiencing a php fatal error when trying to bringing up the elgg software. First of...
    • Could you try with PHP 7.1 instead of PHP 7.2? Final version of 7.2 is not yet out, and it might be that it's a bug in PHP causing this fatal error instead of just a warning as it seems to have been before. Or it might be that Elgg is just not yet ready for PHP 7.2 if there had been some backward incompatible changes made in PHP 7.2 with regards to incompatible method declarations.

    • Php 7.2 is not for production use. 7.1.11 is last stable version. I am using 7.1.8 and Elgg2.3.4

  • Mc replied on the discussion topic Like Button and Popular Blog Post
    Thanks iilony, disabled hypeinteractions and still have error I will look in other areas Thank Bo  view reply
  • Is mod_rewrite installed on the new server and working correctly? If not, it would explain the "The Action File for login was not found?" error message and most likely also the other issues. Also, it looks like your site has been/is... view reply
  • charlie2017 replied on the discussion topic Error when sending private message on Elgg 2.3.2
    I managed to find a solution: For anyone experiencing the same issue. You need to enable the Php-iconv extension on your server.  view reply
  • charlie2017 replied on the discussion topic Error when sending private message on Elgg 2.3.2
    I have also found that the same error appears when I try to add a new user from the administrator view. Could this be an issue with my server configuration? view reply
  • charlie2017 added a new discussion topic Error when sending private message on Elgg 2.3.2
    Hi everyone.  I am having an error on a new installation of Elgg 2.3.2. When I try to send a private message,  The php error is as follows: Fatal error: Call to undefined function Zend\Mail\Header\iconv_mime_decode()...
  • Hello all, I am in the process of moving Elgg 1.8 to a new server, I modified the database tables for the new directory paths etc.  The only issue I am running in to is that everytime I click on Log In, not from the blue menu/top menu but...
    • Is mod_rewrite installed on the new server and working correctly? If not, it would explain the "The Action File for login was not found?" error message and most likely also the other issues.

      Also, it looks like your site has been/is installed in a subdirectory on your old and on the new server. If that's the case you most likely have configured the RewriteBase in Elgg's .htaccess (to fit the subdirectory name on the old server). Have you changed .htaccess to match the new subdirectory name (or set it correctly in case you started with the original .htaccess on the new server)? If the RewriteBase is wrong, it would also explain the "not found" error.

  • adrew22a replied on the discussion topic List only latest entity of each user
    Im trying to use this example I found : SELECT max(id) as id, asker FROM questions GROUP by asker ORDER by id DESC Implemented in Elgg like the following: $content = elgg_list_entities(array(   ... view reply
  • iionly replied on the discussion topic File Upload issue
    It should work on Elgg 2.3.4 without problems if upload_max_filesize and post_max_size as set in .htaccess (or the server's php.ini) are not the restricting factor. The values displayed on the Server Info page (under "Administer" -... view reply
  • iionly replied on the discussion topic SUB GROUP
    @jmperu Learn about how Elgg works: http://learn.elgg.org/en/stable/guides/index.html http://learn.elgg.org/en/stable/design/index.html and then study the code of the subgroups plugin (and likely also the groups plugin) to understand how... view reply
  • iionly replied on the discussion topic Like Button and Popular Blog Post
    The "error" you posted is not exactly an error but just a warning that foreach() loops over an array with 0 items (no results found to work with). It's a bit annoying to get these warnings (could be avoided to happen if checking in the... view reply