The more I use sh404sef with Joomla 1.5.x.. the more I'm convinced that its a buggy piece of crap. Between this and the broken RSS feeds, I'm about ready to look at another SEF component.

I also just installed these two components together ans getting the same problem.

Anyone fix the problem yet?


I have a cover up fix actually somewhat, just make the error appear the same color as the background.
Do a search at http://www.woodworkingadvice.com to see what I did. The error is there but barely noticeable.

With this error, is the revenue part of the ads still working? Not really sure how to test it and still be kosher.

I am having the same problem:

- Warning: Invalid argument supplied for foreach() in W:\var\www\test\administrator\components\com_sh404sef\sh404sef.class.php on line 2182
- The layout of the search page is broken, i.e. after the search results there is some space and then the bottom of the page

If I remove the AdSense ID then there are no problems!
I am using the latest versions (Joomla 1.5.7, sh404SEF 1.0.11_Beta - build_147 - Joomla 1.5.x, com_googlesearch_v1.5.10, mod_googlesearch_v1.5.10), running on local PC.

Again, If I remove the AdSense ID then there are no problems, except that after the search results there is a lot of empty space but the page layout is not broken anymore.

Any hint?

Hello everybody...

I have exactly the same problem. I've posted some words on the sh404 forum. And an administrator replied:

"HI,

This is a bug in the module [googlesearch], as you can see by looking at the source code of your page. You get something like this :

Code:
<form method="get" action="index.php" id="mod_googleSearch">

The action is wrong, it should be an absolute link, like /index.php or yoursite.com/index.php. I suggest you contact the module/comp author about this.
You can also check that the behavior is slightly different if you try do a search from another page than home.

Rgds"

If this can help someone to fix all this up, it would be nice.


fred

I've got the same problem on 1.5.7. Changing the action to "/index.php" or "http://mysite.com/index.php" doesn't affect a thing. I love this component so it would be nice to get this fixed!!

Is this component still being developed? I think think we've heard anything from the author yet.

Okay so I've solved the issue. It is related to sh404sef but I do not think that sh404sef is the problem.

In {public_html_dir}/administrator/components/com_sh404sef/sh404sef.class.php starting at line 2175 there is

Code:

$client =& JApplicationHelper::getClientInfo(JRequest::getVar('client', '0', '', 'int')); //load folder filesystem class jimport('joomla.filesystem.folder'); $path = JLanguage::getLanguagePath($client->path); $dirs = JFolder::folders( $path ); foreach ($dirs as $dir) {

sh404sef is getting the langauage directory from JLanguage which seems to be basing its information on JApplicationHelper::getclientInfo. I'm not very knowledgeable in joomla plugins but for some reason, maybe because the component pulls up google's search page via an inline frame, Joomla cannot determine the direct path to the language folder thus returning "/language" which doesn't exist. So, I've enabled a workaround by adding the following between the $path and $dirs (at line 2179)

Code:

if($path == "/language") $path = "/direct/path/to/language";

Example "/home/myusername/public_html/language". I have no error now!

Kremzeek wrote:
Is this component still being developed? I think think we've heard anything from the author yet.

Hi Kremzeek,

Of course I'm still around.

I've even released some new plugins recently:

- Accordion Menu Apple style

- Accordion Menu Apple style module

- Drop Down Menu Apple style

- Side Bar Menu Apple style

I haven't done anything because I could not replicate the error on my machine, no matter which version of Joomla I tried. (I'm using the English only version.)

Without replicating the error, there's no way I can fix the error.

See, there are already thousands using this module/component. Most of people are not getting the error. Only some of the people are. There must be a reason somewhere. Are those people getting the error using some other languages? Is there anybody using the English-only version also getting the same error?

Is it possible for somebody to show me a sure way of replicating the error?

Regards,
/kksou

Thanks Harty83,
for this dirty trick
At least we can use it now...

I hope kksou will have a look at this to make perfect his great component ;)
He must have understood what's causing it now...
keep on the good work!