piwigo / pem Goto Github PK

PEM manages a list of project extension, submited on a website by users.

PHP 89.45% Shell 0.04% CSS 2.30% JavaScript 2.27% Smarty 3.55% HTML 2.28% Perl 0.10%

pem's Introduction

Manage your photo library. Piwigo is open source photo gallery software for the web. Designed for organisations, teams and individuals.

The piwigo.org website introduces you to Piwigo. You'll find a demo, forums, wiki and news.

Requirements

A webserver (Apache or nginx recommended)
PHP 7.4+. Piwigo can run with PHP 7.0+ but these end-of-life versions are no longer maintained and may expose your site to security vulnerabilities.
MySQL 5 or greater or MariaDB equivalent
ImageMagick (recommended) or PHP GD

Quick start install

NetInstall

Download the NetInstall script
Transfer the script to your web space with any FTP client
Open the script in you web browser (for example http://example.com/piwigo-netinstall.php) and follow the steps

More information

Manual

Download the latest stable version and unzip it
Transfer everything to your web space with any FTP client
Open your website (for example http://example.com/piwigo) and follow the steps

More information

If you do not have your own server, consider the piwigo.com hosting solution.

Contributing

Piwigo is widely driven by its community; if you want to improve the code, fork this repo and submit your changes to the master branch. See our Contribution guide.

License

Piwigo is released under the GPL v2 license. See our Copying details.

pem's People

Contributors

Stargazers

Watchers

Forkers

nikrou klaoun

pem's Issues

Finish install of bugtracker

Reported by mistic100 on 16 Oct 2013 16:24 UTC
Test comment

Don't use the /e modifier with preg_replace

( ! ) Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ./include/Smarty/libs/Smarty_Compiler.class.php on line 270

Archive from Git

Reported by plg on 22 Oct 2014 14:13 UTC
Like SVN, it would be useful to create the revision archive from Git.

Installer script

Reported by Anthon Pang on 16 Oct 2013 17:36 UTC
The current procedure (see doc/README) to install PEM could be greatly automated using an install script, e.g., install/install.php

if include/config_local.inc.php doesn't exist:

form to input database connection information and admin user
create database (if needed/possible)
create tables
configure config_local.inc.php

Account manager

Reported by plg on 16 Oct 2013 17:39 UTC
PEM should be able to manage accounts by itself or at least not depend on punBB for accounts.

Reported by Mathias M on 16 Oct 2013 17:17 UTC
If rights are badly set to upload file, PEM still creates the revision and does not tell you the archive could not be uploaded. So when you click on the download link of the extension, you get a beautiful 404.

Featured extensions

Reported by plg on 16 Oct 2013 17:29 UTC
Ability to set some extensions as "featured".

optimize stats for menu

Currently in include/header.inc.php we're doing some sub-queries select...where field in (select...) : this is very slow.

Remove ability to have users external to MySQL

Reported by plg on 16 Oct 2013 17:24 UTC
User management was designed so that you can have multiple user manager, I mean something else than include/functions_user_local.inc.php.

In practice, no PEM admin has ever tried to use a PostgreSQL database, a flat file or anything to manage users.

As this feature adds constraints (such as no inner join in MySQL queries to retrieve user infos) and brings nothing in practice, I propose to remove this feature.

User entered information lost when one field is missing

Reported by S. Correia on 16 Oct 2013 17:31 UTC
If I submit an extension without having filled in all the fields, then it results in an error and all the fields I have filled in are lost. I must fill them again.

The first things to do would be to mark all fields as required (by using a "*").
Then if something is missing, it would be nice to keep the fields that are already filled by the user.

Don't erase form content when an error occurs

Reported by mistic100 on 29 Dec 2013 20:13 UTC
Add $page infos, warnings and errors (as Piwigo) and keep form contents when there is an error (missing field, etc.)

"I use this extension"

Reported by plg on 16 Oct 2013 17:30 UTC
To make the community more dynamic around the extensions, it would be useful that users can declare which extensions they use. In the extension manager, the user list is displayed, on the forum (for example) the extension list is displayed on the user profile page.

Uploaded screenshot saved with wrong extension

Reported by Anthon Pang on 16 Oct 2013 17:38 UTC
Example: upload "logo.png". It is saved as "screenshot.jpg" even though it's still PNG format. As a result, it is served up with the wrong Content-Type (image/jpeg). It doesn't appear to be a problem for current browsers that use content sniffing.

thumbnail.jpg is fine (JFIF).

The simple fix would be to convert to jpg.

Don't sanitize GET and POST in common.inc.php

Reported by mistic100 on 2 Jan 2014 15:24 UTC
In common.inc.php GET and POST vars are escaped with mysql_real_escape_string
This prevent to immadiately display variables (quotes are escaped, linebreaks are removed, etc.)

It should be removed, and individually escape each variable when necessary

Sort revisions by version

Reported by mistic100 on 7 Feb 2014 10:44 UTC
on extension page, revisions are sorted by publication date, it would be better they were sorted by version

Allow users to report compatibility level of an extension with a specific project version

Reported by Matthieu Helleboid on 16 Oct 2013 17:21 UTC
It would be useful have the possibility to report if an extension is compatible or not with a version of the project without being the developper of the extension.
This way several users are able to test the extension with any version and to report success or failure with a comment and a compatibility level.
Being able to report the quality of the extension would be great also.

Mass modification in "version" field

Reported by S. Correia on 16 Oct 2013 17:34 UTC
When a new release of the product (e.g. Talend Open Profiler) appears, it would be nice to be able to update the versions of the extensions which were compatible with the previous release of the product.

Example:
TOP-1.1.4 is released.
I would like to add the version 1.1.4 to all extensions that were compatible with 1.1.3.

Currently, it's only possible by editing the extensions one by one.

automatic link to Github page if hosted on Github

If the extension is hosted on Github, automatically add a link to the Github page

Protect upload directory from web browsing

Reported by plg on 16 Oct 2013 17:27 UTC
The upload directory should not be "browsable". As you can upload files inside, the permissions have to be "wide", it may attract intruders and let them upload unwanted files and browse them.

In the upload directory, a .htaccess file, with :

order allow,deny
deny from all

PEM source code should use readfile function for screenshots as it already does with the zip files.

Warning : we have to deal with existing remote clients (like plugin manager in Piwigo)