Utility for building access collections on the fly
·
Allows users to easily upload and embed media into text areas. Requires a plugin for uploading files.
Integrates the popular rich text editor CKEditor.
Let users confirm friend requests. Make friends like on Facebook or LinkedIn
· Désactiver
Adds a search capability
Il existe d'autres plugins qui répertorient Search en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci : Search Advanced
·
· Désactiver
Provides group support for elgg
Il existe d'autres plugins qui répertorient Groups en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci : Group Tools,Group Subtypes
Combines different group additions into one plugin.
Group Subtypes
·
Provides a public list of the members of your site
·
Add advanced features to the search
· Désactiver
Adds user profiles.
Il existe d'autres plugins qui répertorient Profile en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci : Profile Manager
Manage your widgets
· Désactiver
A demonstration of how to customize your site's homepage.
Il existe d'autres plugins qui répertorient Front Page Demo en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci :EasyTheme2
·
·
· Désactiver
Adds file sharing to Elgg
Il existe d'autres plugins qui répertorient File en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci : File Viewer,hypeAttachments
Perform database cleanup tasks
· Désactiver
Provides security filtering. Running a site with this plugin disabled is extremely insecure. DO NOT DISABLE.
Il existe d'autres plugins qui répertorient HTMLawed en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci :htmlawed_unfiltered
·
·
Allow iframes and scripts in blogs
Adds the ability for users to invite friends through email.
·
Enables users to like content on the site.
Browse the system event log
Rotate the system log at specific intervals
Adds support for managing subscriptions for user and group notifications
Improved management of user and group profile fields
Adds the option for users to report content and for admins to investigate it.
·
·
·
·
·
Third-party integrations for (pre)viewing files
·
A photo gallery with albums, tagging, and a slideshow.
·
iZAP Videos - revised edition by iionly
Video plugin for Elgg. Supports addition of both on-server and off-server videos.
·
Allows to send out full HTML mails / notifications
·
Generate user accounts from imported CSV file.
Authenticate Elgg users via HybridAuth providers
·
·
Provides a simple chat based on Elgg.
·
·
Access grants
Developer tools for managing and ajaxifying lists
Drag and Drop File Uploads
Feature-rich social interactions for Elgg
URL scraping and embeding services
·
Attachments
File and image handling
Bootstrap for hypeJunction plugins
· Désactiver
User walls
Il existe d'autres plugins qui répertorient hypeWall en tant que dépendance. Vous devez désactiver les plugins suivants avant de désactiver celui-ci : hypeWall Extended, hypeWall-iZAP Videos and Tidypics
This plugin is an extension of hypeWall (https://github.com/hypeJunction/hypeWall) offering more posting options on user's walls. Initial development of this plugin was funded by https://socialbusinessworld.org.
hypeWall-iZAP Videos and Tidypics
Adds menu items to the hypeWall menu for quickly adding videos with the iZAP Videos plugin and photos with the Tidypics plugin.
Adds the ability for users to send private messages to each other.
EasyTheme 2.0
Provides geocompletion where the Elgg location fieldtype is used
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.
Sorry. I simply can't reproduce it.
The only way to get somethink broken at all was by renaming the css config file of Easytheme in path/to/your/data/directory/easytheme2/cssinc.php. Then the page layout was broken quite completely (not exactly in the same way as on your site but similar). The only explanation I would currently have for your problem is that something is wrong with this file on your installation (or maybe even the whole easytheme2 folder in your data directory as you also mentioned a problem with the textright.php file that is also in this folder). Have you tried a fresh installation for testing locally independently of your real site?
yes I even left a local installation of version 2.3.7 and reinstalled the plugins
Sorry to point this out but the version(s) of Tidypics available at the github repo is EXACTLY the same as the version(s) available here at the Elgg community site. So, it makes absolutely no sense to say that it works with the release downloaded from one source while it fails with the same version downloaded from the other source.
Additionally, the fact that you have now an issue with uploading photos both with Tidypics (as mentioned at https://elgg.org/discussion/view/2780917/tidypics) AND also quite a similar issue with hypeGallery (https://elgg.org/discussion/view/2781049/hypegallery) makes me think that the problem on your site might have nothing to do with any of the plugins (hypeWall, Easytheme, Tidypics, hypeGallery) but that there's rather an issue with the Elgg installation or the server configuration that causes your Elgg site to be at least party broken.
So, the question: what have you done immediatelly BEFORE the problems on your site started? Have you upgraded Elgg? Have you moved to another server or changed the location of data directory and/or install directory on the server and/or changed the domain name? Or have there be other upgrades/changes on the server (e.g. php upgrade)?
It might be that
.htaccess
RewriteOptions inherit
# Elgg htaccess directives
<FilesMatch "(nginx|htaccess).dist">
order allow,deny
deny from all
</FilesMatch>
# Don't allow listing directories
Options -Indexes
# Follow symbolic links
Options +FollowSymLinks
# Default handler
DirectoryIndex index.php
############################
# BROWSER CACHING
# Make sure .ico has proper MIME type, allowing mod_expires to handle them.
<IfModule mod_mime.c>
AddType image/vnd.microsoft.icon .ico
</IfModule>
# The expires module controls the Expires and Cache-Control headers. Elgg sets
# these for dynamically generated files so this is just for static files.
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 year"
</IfModule>
# Conditional requests are controlled through Last-Modified and ETag headers.
# Elgg sets these on dynamically generated cacheable files so this is just for
# static files. Note: Apache sends Last-Modified by default on static files so
# I don't think we need to be sending ETag for these files.
<FilesMatch "\.(jpg|jpeg|gif|png|mp3|flv|mov|avi|3pg|html|htm|swf|js|css|ico)$">
FileETag MTime Size
</FilesMatch>
############################
# PHP SETTINGS
<IfModule mod_php5.c>
# limit the maximum memory consumed by the php script to 64 MB
php_value memory_limit 10224M
# register_globals is deprecated as of PHP 5.3.0 - disable it for security reasons.
php_value register_globals 0
# post_max_size is the maximum size of ALL the data that is POST'ed to php at a time (8 MB)
php_value post_max_size 838860800
# upload_max_filesize is the maximum size of a single uploaded file (5 MB)
php_value upload_max_filesize 524288000
# on development servers, set to 1 to display errors. Set to 0 on production servers.
php_value display_errors 0
</IfModule>
############################
# COMPRESSION
# Turn on mod_gzip if available
<IfModule mod_gzip.c>
mod_gzip_on yes
mod_gzip_dechunk yes
mod_gzip_keep_workfiles No
mod_gzip_minimum_file_size 1000
mod_gzip_maximum_file_size 1000000
mod_gzip_maximum_inmem_size 1000000
mod_gzip_item_include mime ^text/.*
mod_gzip_item_include mime ^application/javascript$
mod_gzip_item_include mime ^application/x-javascript$
# Exclude old browsers and images since IE has trouble with this
mod_gzip_item_exclude reqheader "User-Agent: .*Mozilla/4\..*\["
mod_gzip_item_exclude mime ^image/.*
</IfModule>
## Apache2 deflate support if available
##
## Important note: mod_headers is required for correct functioning across proxies.
##
<IfModule mod_deflate.c>
AddOutputFilterByType DEFLATE text/html text/plain text/xml text/css text/javascript application/javascript application/x-javascript image/svg+xml
BrowserMatch ^Mozilla/4 gzip-only-text/html
BrowserMatch ^Mozilla/4\.[0678] no-gzip
BrowserMatch \bMSIE !no-gzip
<IfModule mod_headers.c>
Header append Vary User-Agent env=!dont-vary
</IfModule>
# The following is to disable compression for actions. The reason being is that these
# may offer direct downloads which (since the initial request comes in as text/html and headers
# get changed in the script) get double compressed and become unusable when downloaded by IE.
SetEnvIfNoCase Request_URI action\/* no-gzip dont-vary
SetEnvIfNoCase Request_URI actions\/* no-gzip dont-vary
</IfModule>
############################
# REWRITE RULES
<IfModule mod_rewrite.c>
RewriteEngine on
# If Elgg is in a subdirectory on your site, you might need to add a RewriteBase line
# containing the path from your site root to elgg's root. e.g. If your site is
# http://example.com/ and Elgg is in http://example.com/sites/elgg/, you might need
#
#RewriteBase /sites/elgg/
#
# here, only without the # in front.
#
# If you're not running Elgg in a subdirectory on your site, but still getting lots
# of 404 errors beyond the front page, you could instead try:
#
#RewriteBase /
# If your users receive the message "Sorry, logging in from a different domain is not permitted"
# you must make sure your login form is served from the same hostname as your site pages.
# See http://learn.elgg.org/en/stable/appendix/faqs/general.html#login-token-mismatch for more info.
#
# If you must add RewriteRules to change hostname, add them directly below (above all the others)
# hide all dot files/dirs (.git)
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule (^\.|/\.) - [F]
# Everything else that isn't a file gets routed through Elgg
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule ^(.*)$ index.php?__elgg_uri=$1 [QSA,L]
</IfModule>
RewriteCond %{HTTP_HOST} ^driving\-lovers\.fr$ [OR]
RewriteCond %{HTTP_HOST} ^www\.driving\-lovers\.fr$
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/[0-9a-zA-Z_-]+$
RewriteCond %{REQUEST_URI} !^/\.well-known/pki-validation/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule ^/?$ "https\:\/\/driving\-lovers\.com\/" [R=301,L]
param tidypics serveur
Paramètres : Tidypics
Informations du serveur
droits repertoire serveur DATA
Statistiques : Information du serveur
Serveur web
PHP
Memcache
Memcache is not setup on this server or it has not yet been configured in Elgg config. For improved performance, it is recommended that you enable and configure memcache.
must set memcache in elgg_config.setting.php and how if yes
Maybe it doesn't matter but your .htaccess file is slightly messed up with some rewrite rules duplicated (and some maybe even unnecessary). I think that CPanel also added some rules on its own (which might not be necessary but I don't know if this can be prevented). memory_limit seemed unnecessary high. But maybe the php variable values set in .htaccess are not used on your site anyway (as post_max_size seems to set to 0 as seen from the stats output whereas it is not in .htaccess - maybe the values set in php.ini are used on your server instead - I think with suexec used on the server any php variables values from .htaccess files are ignored). Anyway, the .htaccess does not seem that wrong to explain the photo upload issue.
For completeness you might want to try
(Backup your .htaccess file in any case if it doesn't work with the one I posted! For future reference: in vendor/elgg/elgg/install/config/ you will find the default .htaccess file as htaccess.dist, so you can compare your .htaccess with it when updating the Elgg version to see if something has changed).
For the photo upload issue I would suggest to test with all other 3rd party plugins temporarily disabled to see if it makes a difference. You can also look into the data directory (in the subdirectory of the user you test it with) to see if there any any uploaded image files saved at all (the original uploaded file at least and possibly only the resized thumbnails missing) and only not displayed or if the problem is due to the files not getting saved. On the other hand, if you have already existing images previouly uploaded that got displayed in the past and are now no longer displayed the problem is less likely to be an upload issue.
But regardless what the reason for the problem is, you need to do the testing on your own and you need to narrow down the possibilities. It doesn't help to just telling us what doesn't work (especially not if there are several things not working). You are the one knowing best what you have changed recently and what might be the possibly candidates for the problem(s). If you updated some plugins, try it with these plugins disabled for a start and enable them one at a time only. Check the server error log (with logging enabled in the advanced site settings). Try to figure out if there's a conflict between two plugins (when both being enabled). At least we need to know how to reproduce your problem or it's nearly impossible to really give you a useful feedback.
Again I have checked and again I have found: there's no difference whatsoever in code between Tidypics from here and from github. If you see a difference it might be that you compared different versions (where some changes are surely there) or could it be that you made changes in the code yourself and forgot?
As I wrote in my last posting, I also did not think that the differences in .htaccess would matter (or explain the problem). I just didn't like the duplicate rewrite rules being there. And the redirect rules should be placed above the other rewrite rules to avoid possible problems (at least it's suggested in the comment in .htacess).
The "80887" is the album guid. The folder name is equal the album guid. The image files (of all images of the corresponding album) should be within this folder. The image guid is not part of the image filenames within the album folder. The image filenames consist of a timestamp plus original filename. And the resized image files have an additional prefix (e.g. largethumb + timestamp + original name).
Check if the image files are within the album folder. You should also check the server error log for an entry made at the time of trying to access / display the image on the site. For an error log entry being made you might need to enable debugging output in the advanced settings in the admin area (set the debug level to errors and warnings). The error entry should contain the path where the image file is expected to be. If the path in the log entry doesn't point to the expected location, it would explain why the image file is not found (and in this case it's the question why the expected path is different). But in any case check if the image files are even there in the first place in the data directory. If not, the upload failed and this would be a different matter to deal with than an issue of existing files not getting served.
when a function is Deprecated is what it is not treated or is it just a warning that it will not be used anymore in the 2.3.6 elgg version I'm using plugin provided in 2.2 or these Deprecated function messages
It's "deprecation warnings". These are not errors (yet). They just tell you that a later version of Elgg might (very likely) remove the function used (as it has been replaced by another) and the code would no longer work on this later version of Elgg anymore if not changed. For the time being though, the old function still works (or is at least handled in a way that is backward compatible). The deprecation policy of Elgg is that no backward compatibility breaking stuff is introduced with a minor version of Elgg. This means that the Elgg API within the lifetime of a major Elgg version (e.g. Elgg 2) is not breaking backward compatibility. There might be new API functions added within it's lifetime (i.e. in Elgg 2.1, 2.2, 2.3) but they will not yet replace any functions that got deprecated (but where you might have to expect that they are removed in Elgg 3 for example).
So, if you get a deprecation warning for some code of a plugin released for Elgg 2.2, this plugin should still fully work on Elgg 2.3 (but very likely no longer on Elgg 3.0). Any plugin that has been released for Elgg 2.0 - 2.3 should work on Elgg 2.3 (on newer versions respecitively but not on older 2.x version as stated for the plugin release). I wrote "should work" and not "does work in any case" as there might be a few plugins that do things very specifically that might not hold up with the backward compatibility within a major Elgg release cycle, but these would be really a rare case of plugins (if there even are any of these still).
- Previous
- 1
- 2
- 3
- Next
You must log in to post replies.