Forums

Chronoforms is exactly what I was needing... I installed it on my test site, and combined with Jumi to get some php script into an article for a report, it worked perfectly.

Then I installed it on my live site, and it installed fine, but when I try to access the admin sections for Chronoforms, I get a browser error:

Safari can’t open the page “http://www.headgutcheck.com/administrator/index.php?option=com_chronocontact&act=all”. The error was: “cannot decode raw data” (NSURLErrorDomain:-1015)

When I try to access it with Firefox, I get a blank screen, and no errors listed in the error console.

Omniweb also mentioned the inability to decode raw data.

Although the "test" site is a different domain, it's still part of the same hosting account, so it's on the same server, and they use identical php.ini files. So it doesn't seem as though it could be server setting related.

Any ideas? I'd really like to take what I did on my test site and get it implemented.

Thanks,
Scott<br><br>Post edited by: sinemac, at: 2007/10/29 12:57

Hi Scott,

Never met this issue before, what about IE ? did you try to clear all your browser cache ?🙂

Did you google this error ?

Cheers

Max

Hi Max,

I didn't find anything useful doing a google search, at least, nothing that made immediate sense to me.

I did try clearing caches, and even tried a different computer - same result. I haven't tried IE yet - I'll boot up Windows shortly and give it a shot, but I'm not hopeful.

It seems to me it must be somehow related to the site, perhaps permissions are off somewhere, or some setting that's different that I missed.

The two sites are on the same server, I used the same browser to install the component, I even tried uninstalling and reinstalling it on the site where it doesn't work... it's just weird - I really can't figure out why it works on one site and not the other.face-meh-blank

--edit--
Ignore what I said about googling the error - I googled the "decode raw data" instead of the error code :blush: -- I'll read through what comes up with the code to see what I can learn.<br><br>Post edited by: sinemac, at: 2007/10/29 20:29

Well, it turns out the error I googled and found a number of entries for was: NSURLErrorDomain:-1011, which it seems is similar to a 500 server error.

The error: NSURLErrorDomain:-1015 - didn't have anything useful.

I tried IE and Firefox on Windows - both just return a blank page when I try to access the component.

I guess I'll check with the hosting company to see if they can help track it down... it's gotta be an issue of a server setting somewhere.

--edit--
I decided to try installing it on another site hosted under the same reseller account (i.e., same server as the other two domains) - and it works fine there. :unsure:

I think I'll try a clean Joomla install on the problem site. I'll let you know if that clears it up.<br><br>Post edited by: sinemac, at: 2007/10/29 20:51

I figured it out.

There was one Joomla! setting that was different - on the site that the component didn't work, I had GZip compression enabled in the Joomla! admin. but not on the other sites. So I disabled that, and now it works.🙂

Great news!! Sinemac, could you please post the steps you took to fix it so all users face the same problem can fix it too ?😉

thanks!!

Sincerely,

Max

In the Joomla! administration, under Global Configuration -> Server
disable "GZIP Page Compression" and then Save.

I don't know whether this is an issue with the Joomla! 1.5 RC3 build in general, or something with ChronoForms in particular (I haven't experienced the problem with any other components - not that there are that many J!1.5 native components yet), but my hope is that by the time Joomla! 1.5 is final (or very shortly thereafter) this incompatibility will have been addressed.

Hi Sinemac,

Sure, I will track this and know what exactly causes it🙂

Thanks!!

Max

Just thought I'd let you know that this is still a problem with Joomla! 1.5.1 and ChronoForms - enabling gzip still leads to that error.

Hi Sinemac,

We still have no new version for J1.5 yet but we are trying to track this issue!

Cheers,

Max