Upgrade failed - Orca language compile

I tried to upgrade to 6.1.3 in the hopes it would solve my field builder problem.  I should have know better than to think it would work.   I got this error when I went to Orca in admin panel, and when I try to compile the language I get "language complication has been failed- please check folder permissons"  - I tried to change the directories and files in question to 666 or 777 - but it didn't work.  Any suggestions?

Quote · 20 Jul 2008

The "headers already sent" error is usually caused by having white space before or
after the opening and closing PHP tags (<?php . . . ?>).

Quote · 21 Jul 2008

I had the same problem after update one of my sites.... I had to set back a backup.

Kids first
Quote · 21 Jul 2008

I tried to upgrade to 6.1.3 in the hopes it would solve my field builder problem.  I should have know better than to think it would work.   I got this error when I went to Orca in admin panel, and when I try to compile the language I get "language complication has been failed- please check folder permissons"  - I tried to change the directories and files in question to 666 or 777 - but it didn't work.  Any suggestions?

I get this same error! Posted the error in ORCA forum.

Quote · 25 Jul 2008

I had the compiling error when I did a FRESH install of 6.1.3.

After deleting the install, database and all....

I installed V6.1.1, then upgraded patch by patch to V6.1.4....

Languages compiled...and all appears well at the moment.

Quote · 27 Jul 2008

Scratch this post...see the below post for possibly a better sollution.

DialMe.com - Your One and Only Source For Boonex Dolphin Tutorials and Resources
Quote · 28 Jul 2008

Ok guys scratch the previous post with the 666 permission.

Here is another thought that don't require the 666 permision and works for me with the standard 644.

Make sure you are not logged into your orca admin area first. Dolphin admin panel should be fine just don't go to the orca admin area yet.

Now First rename:
/orca/conf/params.conf

To
/orca/conf/params-bk.conf

So you do not have a params.conf file anymore. Only params-bk.conf

Once you do that go to you orca admin area in admin panel. A new params.conf file should be created with hopefully a 644 permission and the warning/errors should disappear. You might recompile the "en" language for the heck of it as long as you are here too.

It's almost like there is some kind of cache type of thing and this does away with it.

Anyway I'd try this. A 644 is always better than 666.

gameutopia

http://www.dialme.com for all your dolphin needs!!

DialMe.com - Your One and Only Source For Boonex Dolphin Tutorials and Resources
Quote · 28 Jul 2008
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.