Quote:

Script_Fu:
Most of the time that is caused because some templates don't follow html standards and the script/hack can't detect the image to replace its link correctly.

I've tried to fix those problems as soon as I find them (or someone reports them), but you would be surprised how many modules and templates out there violate HTML standars and even XOOPS module design rules.

You can check my test sitehttp://www.wtmmail.com and you would see the hack works fine with News Module and the template I'm using.

Quote:

Just my two cents.... Google used to be the Grand Ma of all the search engines, the only one who was important. This has changed a lot... A big part of google search traffic was coming from Yahoo and recently they split and Yahoo started using their own search engine database.

This was long expected and anticipated as they bought Inktomi, Altavista, Fast and Overture a long time ago.

Hi:

For those of you who had problems with this hack when calling your domain fromhttp://domain.com if XOOPS is installed athttp://www.domain.com there is a patch released by XOOPS Developers.

As I said before, this error was not caused by my hack even when it jumped out right after using it.

The url with the instructions is at:
http://sourceforge.net/tracker/index.php?func=detail&aid=898776&group_id=41586&atid=430842

Even if you are not using my ShortUrls hack you should apply this patch to avoid getting a blank page or a "module not found error" if you try to access your site with a subdomain other than the one specified at XOOPS Installation.

Shivaji:

Thanks for your suggestions.

What we (Carnuke and me) meant by "module selective" is that you would be able to turn off the hack for some modules if they don't work properly well, but the hack will still "dynamically" support every module.

As Carnuke said, not everybody follows the guidelines when programming modules and sometimes not even for something so simple as designing a template.

This would make supporting modules easier and less time critical. For example, if Mr.XYZ releases a module tomorrow called IncrediModule and for some reason it does not work fine with hack, you would just turn off support for that module and everyone would be happy.

I still don't know if this would prevent all errors from happening as a "Rewritten" module would still link to a non-compliant module using Rewritten urls... for example, News module would link to IncrediModule as:
http://www.yoursite.com/m-IncrediModule+index+.html

I'll see how it goes after I put together a few more lines of code

Hi:

Just wanted to let you all know I'm currently working in the next version.

The only major update planned is the ability to select which modules the hack should apply the Url Rewriting.

I'll also try to make this new version compatible with XOOPS installations within a dir, but I can't promise it as my time is currently limited.

Amanda:

I'm sorry I can't help you much with this problem you are having with Apache. I don't know much about Apache's configuration directives and sometime ago, I used to have Apche installed at my PC (windows 2000 and XP later) and I stopped doing it because it always acted in a non expected or erratic way. I'm not saying Apache has problems with Windows, I'm just saying that was my experience with it. I got so frustrated, I decided to test my scripts/sites/programs directly online (Linux+Apache).

Maybe if you read Apache Documentation, you may find information about how to get Rewrite module to work.
http://httpd.apache.org/docs-project/

Greg:

I have never tested it with a version other than 2.06
I'm afraid I really don't know if it would work

If you test it, please let me know how it goes.

Carnuke:

1) My test site URL ishttp://www.wtmmail.com
you can download V0.4 at the following url:
http://www.wtmmail.com/XoopsShortUrls/ShortURLs_0.4_for_Xoops.zip

I can't remember if last fixes are included into this distribution, but anyway, here they are:
http://www.wtmmail.com/XoopsShortUrls/xoops_shorturls.txt7
http://www.wtmmail.com/XoopsShortUrls/loadpage.txt7

2) Already answered this question above.

3) That is the drawback to V0.4, it rewrite urls in a different longer way
I'm sorry about this change, but there were too many incompatibities with some modules which were not properly written.
The upside to V0.4 is its "dynamic" compatibility with old and new modules.

Quote:

Phppp:
I agree with you, there is not reason why this hack would make XOOPS faster. In my own testings, it adds an unnoticeable delay of around 0.0042 seconds but your mileage may vary.

Greetings everybody

I'm sorry I'm been absent from these boards for quite some time. I'm been pretty busy working with some new projects and haven't had any free time to work with this hack.

Carnuke,
from v0.3 to v0.4 there was a huge jump. In version 0.3, the hack was only compatible with a few modules while in v0.4 the hack was "dynamically" compatible with every module. Please note I say dynamically between quotes because some modules are not 100% template based or have some errors in their templates/html pages and those "errors" jump out when using the hack.

Right now the only error/problem I've been unable to fix is the one causing a domain to work incorrectly if you use a different name, for example:
if your XOOPS installation says the domain is "www.yourdomain.com" and you try to access it as "yourdomain.com" (without the www.) you get some weird errors. Until now I have been unable to trace and fix this error. (this answers wrtravel question).

Carnuke, I would also like to clarify that the .txt files you can download from my site, are simple fixes to some problems encountered. Right now the last fix is #7. I'm can't remember if fix #7 is already incorporated into the distribution pack for V4.

I'll be checking this forum for a few days, so if anyone have a question about this hack, please feel free to post it and I'll do my best to answer. If you are reporting an error, please be sure to do the following:

* Post as much information as you can regarding the error.
* Describe what you were trying to do.
* Post what version of the hack you are using and if you are already using any of the fixes.
* Post the exact URL where you are getting the error.
* If posting the URL, please make sure I don't have to register to your site in order to see the error/url (aka. give the module anonymous rights)

I'll change my info so I can get an email everytime someone post to this forum. That way I can answer messages faster.

Thanks to everyone who is testing this hack, specially, those who had the patience to deal with it since its first version

(English is not my primary language, so any concordance/grammatical error is not intended, LOL)