I install my component and it install okay. When I go to open the componeny I get the following error:

0
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, This email address is being protected from spambots. You need JavaScript enabled to view it. and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Am I missing a setup step?

Steve

Are you talking about running sandbox or local. Either way, try in local and switch on debugging - that should give you a few clues...

Gez

The component works in the sandbox. I downloaded the build and installed it on a test website. It at first errored out on the first install on the test website but installed the second time I tried. The admin part of the back end opens but I get the error noted when I try to access the component. I get the same error when I try to access the component from the front end of the website.

/**REMOVED CREDENTIALS**/

OK, just logged in and tried both your COOK components and get the same thing.

Can you configure your server to allow error reporting? I just tried to enable this in Joomla but it seems as if the errors themselves are being suppressed in favour of the generic response we're getting at the moment.

If you can't switch on more transparent reporting on your server, try installing it locally with reporting on (all) and let me know what errors it reports.

Thanks,

Gez

I didn't see where to set to allow for error reporting from my hosting account. I tried the component install on a different Joomla 2.5 site and it worked fine. Not sure what the issue is...

This can be resolved by using
within your php.ini file assuming that you have access to it via your hosting package.
Note that this setting will affect all sites on your server not just the one with the JC component.

Look under "Scripting" in the control panel of your webhost.

Good luck
vlemos

@vlemos,

I just want to check with you, in the thread: www.j-cook.pro/forum/32-trouble-shooting...mit=10&start=20#6652 , were you experiencing the same behaviour/error as @sgower? The only reason I ask is that the symptoms are different but your solution is the same and just wondered if you posted in wrong topic mistakenly because of their similar titles or in fact, you were experiencing the same.

Many thanks,

Gez

Hi Gez

I can post this solution in both sections. I got these two seemingly different errors from two different servers in response to two different j-cook components. However, the solution was the same.

1. the "DOM" error from a www.networksolutions.com server
2. the "Internal Server Error" from an www.ipower.com server

The networksolutions.com server offers access to a shared php.ini file and we needed to set "asp_tags = off" to get one component to work not knowing how this will affect 100 or 1000 other sites which share this server. Also networksolutions.com warrens that settings which adversely affect other clients will be removed and the account may be discontinued. See here

To me, this is a big issue. This needs a component specific solution: a way of telling the component how to operate internally. You don't want to "nuke" a country to rid one small town of a few rodents.

Regards
V

Hi @vlemos,

Thanks for clarifying and sharing! K++!

Sure, I understand the implications if you're on a shared server. The solution in this case is to use a htaccess directive which will localise the asp tags setting inside joomla htaccess.

Best of luck,

Gez

Hi Gez,

Thanks, you are a good guy. However, the .htaccess solution did not work for me on the servers I work with. It broke the site completely. Before making this change the site worked fine but the component failed. After the .htaccess setting was applied nothing worked.

Regards
V

The solution in this case is to use a htaccess directive which will localise the asp tags setting inside joomla htaccess.

Really?

Are you sure that the htaccess was properly configured? I'm no expert on server-side stuff but, I sure remember when I had to configure a htaccess for the first time it was a bit of a learning curve.

Did you set joomla config to pick up the fact that you were using a htaccess?

What errors were you getting?

Can you access server logs?

Gez

@vlemos,

if you wanna skype me (see profile for contact) I'll take a quick look if you can share your screen.

Best wishes,

Gez

Hello Gez

Sorry I did not see your response before; I was off for the last few days.

Thanks, I appreciate the offer and will organize it.

Regards
vlemos

No probs!

Catch you soon!

G