Simply the best auto RSS to Joomla content importer.

Quick support from the developer with new releases with suggested features.

Surly CiviCRM is great, and I love it, but it is too hard to install on a normal server. CiviCRM is not Joomla friendly!

The file is too large and the installation takes too long so several timeouts are reached in the PHP. The workaround is to increase the timeouts before installing and decreasing them after the install. This you can only do if you have your own server or the hoster gives you access the php settings.

I recommend that the team behind CiviCRM rethink the installation – perhaps install the core of CiviCRM and move the rest to a second installation (like for example done in the JCE plugins, not said that the JCE plugins are demanding), perhaps with the use of Ajax so the execution timeout is not reached.

SH404SEF really blasts every other SEF system away. When SH404SEF was not around I used OpenSEF until it felt apart. After that I tried other SEF systems and later on I finally found SH404SEF.

In the beginning SH404SEF was just a little better that the other SEF systems but a ½ year ago or so his work accelerated and is now light years away from the other SEF systems. Yannick is now integrating relevant security around the SEF core. Brilliant!

Mosconfig attacks from bots were filling up my clients’ log files until I upgraded one of the sites to this version and discovered that SH404SEF now blocks “mosConfig var in URL”-attacks, which therefore is not logged anymore! Great! Now we can focus on the real errors in the log.

Hey take a look what else SH404SEF blocks:

Base64 injection
Script injection
Illegal standard vars
remote file inclusion
IP address denied
User agent denied
Too many requests (flooding)
Rejected by Project Honey Pot
PHP, but user clicked

If Yannick continues on this way of improving the security of Joomla (which should be adopted into the core of Joomla), we are soon going to have the best SEF and the best firewall integrated into one system. It can very well be that this has already happened – I have not had time to test it through.

One minor thing is that my clients keep finding / using chars in their content titles that are invalid chars in the url, which SH404SEF does not replace (before you insert them manually) and therefore gives a real 404 error. SH404SEF does replace some invalid url chars, but fare from all. I would recommend another approach - replacing every char that is not in A-Z and 0-9 or is “_” or “-“.

Great component, precisely what we were looking for :-)

Suggestions to the next release:

1) Option to hide the e-mail addresses of the authors in the display, when people write to them. Most people don't like having they e-mail address visible to the public (even though the write and contact access can be disabled for guests).

2) Create integration with one or more of the best PMSs.