SEF_URLs plugin for cpg1.5.x

[Joachim Müller]

In cpg1.4.x, the SEF_URL plugin used to be part of the coppermine package, although there are known issues with it. That's why the dev team decided to not bundle the SEF_URL plugin with cpg1.5.x any longer.
Instead, it is available here for download. Please keep in mind that this plugin is still experimental and not recommended for production use.

What it does: this plugin makes search engine friendly URLs for index, thumbnails, and displayimage.php. It can only work on apache-driven webservers.
If you have issues using this plugin, uninstall it (using the plugin manager) and remove the .htaccess file from coppermine's root folder that the plugin has created.

Download: http://sourceforge.net/projects/coppermine/files/Plugins/1.5.x/cpg1.5.x_plugin_sef-urls_v1.4.zip/download

Download latest SVN snapshot (use at own risk)

[Timos-Welt]

- fixed: didn't work for displayimage.php
- added: didn't t include the latest stable changes from the cpg 1.4.x version
- fixed: install / uninstall functions didn't work as intended (no use of Inspekt)

Changes in detail:

Changes needed in codebase.php:

Edit: Removed changes because they are in the current version

[Timos-Welt]

I've added another small change to the version in the message above; theme selection wasn't possible (now it is).

[Paver]

@Joachim: Maybe the SEF_URLs plugin should be added to the SVN repository plugins branch so that Timo can commit the changes directly?

[Joachim Müller]

I can add the plugin to the SVN, but this will of course not grant Timo write access there.

[Fabricio Ferrero]

I'm thinking of use this plugin when CPG v1.5 be ready for production and submit the bugs here. I'm a fan of SEO and CPG needs a boost on this topic to keep up to date in front of all new scripts and CMS out there.

Does the Timos' modifications has been added to the first post? Or do I just checkout from repository? (If the plugin was already submited.)

[Joachim Müller]

Please perform a checkout and try for yourself. I don't think that Timo's suggestions have made it into the SVN yet, but you should just try for yourself.

[Joachim Müller]

The sef_urls plugin hasn't existed in the SVN plugin repo, so I added it a few seconds ago. Please feel free to improve as suggested above.
Web SVN: http://coppermine.svn.sourceforge.net/viewvc/coppermine/branches/cpg1.5.x/plugins/sef_urls/
Subversion Repository: https://coppermine.svn.sourceforge.net/svnroot/coppermine/branches/cpg1.5.x/plugins/sef_urls

[Timos-Welt]

updated to v1.3 and attached new version to first post

[Timos-Welt]

updated to v1.6 and attached version to first post

- fixed a lot of URLs
- added known issues text file
- added localisation support for german language

[Timos-Welt]

updated to v1.7

- removed slideshow URLs because not relevant for search engines, improving the plugin's perfomance
- removed sort string from german htaccess (wasn't used) improving performance

[Timos-Welt]

I've updated the SVN version to 1.8 adding experimental support for french and spanish SEF URLs. It would be nice if a french or spanish speaking person could check if these work as they should (and if my translation is good enough).

[Fabricio Ferrero]

I'll check out when I got home and I'll post my results this night!

[Fabricio Ferrero]

One day later, but here I'm! I'm having some troubles with my computer so I'm posting this tiny thing I found so far, if I keep testing and founding new bugs or bad spanish wording, I'll post them...

The little button referring the Plugin's threads on the plugin manager leads to "http://forum.coppermine-gallery.net//index.html/topic,42568.0.html". Please, take out one slash there becase it's giving me a 404.

[Fabricio Ferrero]

OK, Rookie question: How am I supposed to see the plugin working in Spanish? Where does the plugin takes the language from?

If it's from the browser I got in spanish and I don't see the url in sp.
If it's from the cpg installation, despite we know that because someone's fault we don't have the file yet, I duplicated the english one and went to the config panel and chose it. Even that, I don't see spanish url.

Yes, I got the SVN version, 1.8 installed

[Fabricio Ferrero]

"http://forum.coppermine-gallery.net//index.html/topic,42568.0.html". Please, take out one slash there becase it's giving me a 404.

AND... change the ".html" to ".php".

Or, just copy and paste the URL of this post!

Didn't tested when I posted... My bad!

[Joachim Müller]

Haven't looked into the plugin in detail, but as far as I can see the possible scope of i18n of this plugin could be transliteration - it should be able to cope with Spanish pecularities in writing, e.g. accented characters and ñ in case that it should allow filename -> title relations in the future.
As of now, the differences lie in the naming of particular pages:

• search
• contact
• toprated
• topn
• lastcomby
• lastcom
• page
• usermgr
• profile
• thumbnails
• displayimage
• lastupby
• lastup
• slideshow
• top_display_media
• usermgr

For you as a native speaker you just open ht-spanish.txt with a plain text editor and review each line like

Code Select Expand

RewriteRule busca.html(.*) search.php$1 [NC]if "busca" is actually the correct translation for "search" or if it should read buscar or busco. Pretty straightforward

[Timos-Welt]

OK, Rookie question: How am I supposed to see the plugin working in Spanish? Where does the plugin takes the language from?

Please read the known issues txt file!

[Αndré]

AND... change the ".html" to ".php".

'.html' is correct, as you can see in your address bar: http://forum.coppermine-gallery.net/index.php/topic,42568.0.html

[Timos-Welt]

To elaborate it: The german, french and spanish language words have to be tested very carefully. For example, the word 'comentaire' in ht-french.txt is misspelled consciously, because 'commentaire' would contain the word 'comment' which is forbidden because it is used at other places in URLs, too. The question is, if a french visitor would prefer 'comentaire' over 'lastcom' even if it is misspelled. The german version is used here for example without any problem.