piwigo / pem Goto Github PK
View Code? Open in Web Editor NEWPEM manages a list of project extension, submited on a website by users.
PEM manages a list of project extension, submited on a website by users.
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.
Reported by plg on 16 Oct 2013 17:29 UTC
Ability to set some extensions as "featured".
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
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 plg on 16 Oct 2013 17:40 UTC
Instead of manually creating the RSS feed, use feedcreator.class.php
Currently in include/header.inc.php we're doing some sub-queries select...where field in (select...)
: this is very slow.
Reported by mistic100 on 16 Oct 2013 16:24 UTC
Test comment
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.)
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.
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.
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.
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.
If the extension is hosted on Github, automatically add a link to the Github page
( ! ) Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in ./include/Smarty/libs/Smarty_Compiler.class.php on line 270
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
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:
In addition to zip files
Reported by plg on 16 Oct 2013 17:34 UTC
The compact view displays some revisions that are not compatible with the selected version. A revision is list only if it belongs to an extension that is compatible with the selected version.
For example, if "extension 1" has "revision 1" (compatible with version A and B) and "revision 2" (compatible with version B and C). If I filter on version C, then "revision 1" is listed, but it should not.
Reported by plg on 16 Oct 2013 17:18 UTC
It happens that an extension is integrated in the extended application. It would be useful to register this information.
Reported by plg on 16 Oct 2013 17:22 UTC
When adding a file with a too big file and the filesize exceeds the PHP setting upload_max_filesize, the error is not obvious.
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.
Reported by plg on 16 Oct 2013 17:40 UTC
Some references to PhpWebGallery are still present in the code. They have to be removed.
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)
Reported by plg on 22 Oct 2014 14:13 UTC
Like SVN, it would be useful to create the revision archive from Git.
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.
Reported by plg on 16 Oct 2013 17:19 UTC
It would be better to use Markdown syntax for extension/revision description.
Are at least basic html.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.