easytheme2 tipypics

 
Hello,
my theme is easytheme2 as well as tidypics with many other plugin series hype for the wall my problem is that the display of the elements of the pages is not done under the heading of the theme but inside this one do you have an idea to solve this problem?
cordially
voici la liste des plugins

·         ACL Builder Utility 

Utility for building access collections on the fly

·          

·         Désactiver

Embed 

Allows users to easily upload and embed media into text areas. Requires a plugin for uploading files.

·         Désactiver

CKEditor 

Integrates the popular rich text editor CKEditor.

·         Désactiver

Friend request 

Let users confirm friend requests. Make friends like on Facebook or LinkedIn

·         Désactiver

Search 

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

Groups 

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

·         Désactiver

Group Tools 

Combines different group additions into one plugin.

·         Désactiver

Group Subtypes 

Group Subtypes

·          

·         Désactiver

Members 

Provides a public list of the members of your site

·          

·         Désactiver

Search Advanced 

Add advanced features to the search

·         Désactiver

Profile 

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

·         Désactiver

Widget Manager 

Manage your widgets

·         Désactiver

Front Page Demo 

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

File 

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

·         Désactiver

Garbage Collector 

Perform database cleanup tasks

·         Désactiver

HTMLawed 

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

·          

·          

·         Désactiver

htmlawed_unfiltered 

Allow iframes and scripts in blogs

·         Désactiver

Invite Friends 

Adds the ability for users to invite friends through email.

·          

·         Désactiver

Likes 

Enables users to like content on the site.

·         Désactiver

Log Browser 

Browse the system event log

·         Désactiver

Log Rotate 

Rotate the system log at specific intervals

·         Désactiver

Notifications 

Adds support for managing subscriptions for user and group notifications

·         Désactiver

Profile Manager 

Improved management of user and group profile fields

·         Désactiver

Reported Content 

Adds the option for users to report content and for admins to investigate it.

·          

·          

·          

·          

·          

·         Désactiver

File Viewer 

Third-party integrations for (pre)viewing files

·          

·         Désactiver

Tidypics Photo Gallery 

A photo gallery with albums, tagging, and a slideshow.

·          

·         Désactiver

iZAP Videos - revised edition by iionly 

Video plugin for Elgg. Supports addition of both on-server and off-server videos.

·          

·         Désactiver

HTML Email Handler 

Allows to send out full HTML mails / notifications

·          

·         Désactiver

CSV User Import 

Generate user accounts from imported CSV file.

·         Désactiver

Elgg HybridAuth 

Authenticate Elgg users via HybridAuth providers

·          

·          

·         Désactiver

Elggchat 

Provides a simple chat based on Elgg.

·          

·          

·         Désactiver

Access Grant 

Access grants

·         Désactiver

hypeLists 

Developer tools for managing and ajaxifying lists

·         Désactiver

hypeDropzone 

Drag and Drop File Uploads

·         Désactiver

hypeInteractions 

Feature-rich social interactions for Elgg

·         Désactiver

hypeScraper 

URL scraping and embeding services

·          

·         Désactiver

hypeAttachments 

Attachments

·         Désactiver

hypeFilestore 

File and image handling

·         Désactiver

hypeApps 

Bootstrap for hypeJunction plugins

·         Désactiver

hypeWall 

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

·         Désactiver

hypeWall Extended 

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.

·         Désactiver

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.

·         Désactiver

Messages 

Adds the ability for users to send private messages to each other.

·         Désactiver

EasyTheme2 

EasyTheme 2.0

·         Désactiver

Location Geocomplete 

Provides geocompletion where the Elgg location fieldtype is used

 

  • 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
  •  
    my problem is solved by putting this version of the tidypics plugin https://github.com/iionly/tidypics but I can not load the photos this being another problem thanks for your collaboration in search of this display problem I'm going to open another topic for loading images
     
  • 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

    • the GD php extension is missing on your server for some reason now (while it might have been present before). You can take a look on the "Server information" tab on the Tidypics plugin settings page. Do you see an "Enabled" for GD (you would need this extension at least for Tidypics as you have selected this image library to be used in the Tidypics plugin settings - and possibly the GD extension would also be required for hypeGallery).
    • what's up with the data directory? Are you sure it is accessible/readable/writeable by the webserver? This might not be the case if you made any changes in its location or moved your site from another server. Does the "Advanced Settings" page show the correct path to the data directory (again: if you moved your site from another server, this might not be the case if you haven't updated the database entries as explained in Elgg's migration instructions). Do profile images show up correctly (if not there's some read issue from the data directory)? Can you upload files (try with a filetype other than an image file) using the bundled Files plugin (to test if there's an issue with permissions of data directory).
    • What's up with memory_limit, upload_max_filesize, post_maxsize values? Are they set to sufficient large values (you could see the values used by Elgg either on the "Server Information" tab of Tidypics or on the "Server Info" page of the "Statistics" section in the Elgg admin area).
    • If you have upgraded Elgg, have you upgraded Elgg's .htaccess file correctly / at all? If you have upgraded, have you executed all the upgrades of Elgg correctly?
  • .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

    Version de PHP 5.6.33  
    GD Activé Elgg a besoin que l'extension GD soit chargée
    imagick Désactivé  
    exec() Activé Nécessaire pour la ligne de commande d'ImageMagick
    Mémoire disponible pour PHP 1024MB Augmentez la valeur de memory_limit
    Mémoire utilisée pour charger cette page 7.78 MB Ceci est à peu près le minimum par page
    Taille maximale des fichiers à envoyer sur le serveur 0.00 KB Taille maximale d'une image chargée sur le serveur
    Taille maximale des requêtes POST 0.00 KB Taille maximale d'une requête POST = somme des tailles des images + formulaire HTML
    Durée maximale de saisie -1s Durée qu'attend le script avant la fin de l'envoi des fichiers
    Durée d'exécution maximale 7200s Durée maximale d'exécution d'un script
    GD imagejpeg Activé  
    GD imagepng Activé  
    GD imagegif Activé  
    EXIF Activé

    droits repertoire serveur DATA

     

    Statistiques : Information du serveur

    Serveur web

    Serveur : Apache
    Emplacement du journal :  
     

    PHP

    Version de PHP : 5.6.33
    Emplacement du fichier PHP .ini : /opt/alt/php56/etc/php.ini
    Journal PHP : error_log
    Mémoire disponible : 1,073,741,824
    Mémoire utilisée : 7,694,360
    Taille maximum d'un envoi POST : 1,073,741,824
    Taille maximale d'envoi : 1,073,741,824 
     

    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

     

     
    I did not move the site, or update elgg on the remote server just added and deleted x plugin to do different test
     
     
    it's still amazing I can load an image on the wall but it does not work in albums.
     
  • 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

    # 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
    # Don't forget to keep these two IfModules in sync!
    #
    <IfModule mod_php5.c>
        # If using PHP 5.6

        # limit the maximum memory consumed by the php script to 64 MB
        php_value memory_limit 512M
        # 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 200M
        # upload_max_filesize is the maximum size of a single uploaded file (5 MB)
        php_value upload_max_filesize 100M
        # on development servers, set to 1 to display errors. Set to 0 on production servers.
        php_value display_errors 0
    </IfModule>
    <IfModule mod_php7.c>
        # If using PHP 7.x

        # limit the maximum memory consumed by the php script to 64 MB
        php_value memory_limit 512M
        # 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 200M
        # upload_max_filesize is the maximum size of a single uploaded file (5 MB)
        php_value upload_max_filesize 100M
        # 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

    # Not sure if the inherit rule is needed (I think would be useless if there is no .htaccess in parent directory)
    # maybe got added by CPanel
    RewriteOptions inherit

    # 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)

    RewriteCond %{HTTP_HOST} ^driving\-lovers\.fr$ [OR]
    RewriteCond %{HTTP_HOST} ^www\.driving\-lovers\.fr$
    RewriteRule ^/?$ "https\:\/\/driving\-lovers\.com\/" [R=301,L]

    # I think this line gets added by CPanel automatically (and possibly messes up .htaccess rewrite rules)
    RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$

    # explicity allow access for the .well-known directory
    RewriteRule "^.well-known/" - [L]

    # hide all dot files/dirs (.git)
    RewriteRule (^\.|/\.) - [F]

    # Everything else that isn't a file gets routed through Elgg
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d

    RewriteRule ^(.*)$ index.php?__elgg_uri=$1 [QSA,L]

    </IfModule>

    (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.

  •  
    the difference between the two tidypics that have the same version it is this programming which is in comment in the other file start.php // Extend CSS elgg_extend_view ('css / elgg', 'photos / css'); elgg_extend_view ('css / admin', 'photos / css');
     
     
    I made the modifications with the .htaccess it does not change anything
     
    witch tidypics
     
    locally when I load a photo I see well in the data directory of the user the image and the thumbnails
    This image failed to load
     
     
    here is what I have in the address bar on my server https://driving-lovers.com/photos/image/80888/test while the file path is / Public_html / rs / data / 1/36 / image / 80887 we do not have the same value on one side 80888 and on the other 80887 it's normal ?
     
  • 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).