Plugins that are supposed to work on Elgg 3.0 should also work on Elgg 3.1-3.3.
As for my plugins (Tidypics, iZAP Videos, Elggchat etc.) I had no time yet to upgrade all of them to Elgg 3. The plugins I released a 3.0 version of should work on Elgg 3.0-3.3 (but I had not even time to test on Elgg 3.1 or newer!). The plugins I did not make a 3.0 release yet are very likely NOT working on Elgg 3 at all without changes.
For Tidypics and iZAP Videos Rohit made pull requests on github which updates and they should work on Elgg 3. You could try it with these version for the time being (download from https://github.com/rohit1290/tidypics/archive/master.zip and https://github.com/rohit1290/izap_videos/archive/master.zip and renaming the plugin folders after unzipping to match the plugins' names). I hope they work without issues but I could not try them myself. I DO have the intention to update all my plugins for Elgg 3 as soon as have the time to do so and I will very likely build up on the work of Rohit then to make the work go faster.
As for the other plugins of mine I'm afraid I can't offer a working solution for Elgg 3 for the time being.
The hype*-plugins are not longer officially supported. Ismayil released updated versions of his plugins for Elgg 3 though before he stopped his development efforts. You can find the new releases only on github though. For hypeWall see https://github.com/hypeJunction/Elgg3-hypeWall/releases.
Hi completed the install and in the last step it said:
Your Elgg site is now ready to be used. Click the button below to be taken to your site.
But when I click ont that button I see a blank page with that message:
The requested URL was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
If mod_rewrite is now installed and enabled there still might be one or two modifications in your server configuration necessary. Firstly, the rewrite rules defined by Elgg in its .htaccess file can only be working if you allow their use in the webserver config. Now it depends on how your server is set up where you might have to make the necessary adjustment.
One possibility could be to make the change in Apache's main config file (e.g. /etc/Apache2/http.conf but might be located elsewhere on your server). If you have added a virtualhost config with a separate config file for your Elgg site you would proably want to add the necessary configuration to the vitualhost config file. What you would have to add are the following lines
<Directory "/path/to/install_directory/of_your_Elgg_installation">
AllowOverride All
</Directory>
with the path given matching the path to the install directory of your site on your server.
Secondly, if you installed your site in a subdirectory on your server's domain, you probably need to change the RewriteBase value in Elgg's .htaccess file (hidden file in the install directory of your Elgg site). There're instructions and an example given how you would have to set the RewriteBase variable.
Thank you Iionly for your help.
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.