I can't load my Application in a new server

Login or register to post comments
6 replies [Last post]
Offline
Joined: 12/30/2009

Hi,

I'm trying to host my application in a new server, the specifications are:

Apache/2.2.14 (Ubuntu)
Versión del cliente: 5.1.41
extensión PHP: mysqli

We have copied the files in the server and run the index.php file in order to create the connections between QCubed and the DataBase. I get the next message:

Here's what you need to do:

Set the __SUBDIRECTORY__ constant in /includes/configuration/configuration.inc.php. Most likely value: "/assets"

I have changed the value in the configuration file but it doesn't change.

If I try to push the button "I'm done. Continue" nothing happens.

In the other hand, if i click on the link "Ignore these warnings and continue" something happens and the start_page doesn't load. I just get a blank page.

Which error can I making there?. Is it possible that the error is because the php version or the type of server we're using to host the application and the DataBase?

jmirancid's picture
Offline
Joined: 04/04/2011

Hi spike,

Are you using some sub-domians in the host?

Offline
Joined: 12/30/2009

No, I'm not using subdomains. We have the application running on one host but we have to migrate it because there are some memory problems. So, We migrated the DataBase and uploaded the application in the host.

When we load any html or php file using the host ip's address it works without any problem, but, when we try to do the same with Qcubed's .php files it doesn't do anything. It just loaded the index.php file, but as I said in the question, the next pages remain blank.

Offline
Joined: 12/30/2009

Now we're getting a page with the next error code:

Error in PHP Script

/assets/_core/php/_devtools/config_checker.php       PHP Version: 5.3.2-1ubuntu4.9;  Zend Engine Version: 2.3.0;  QCubed Version: 2.0.1 Development Release (QCubed 2.0.1)

Application: Apache/2.2.14 (Ubuntu);  Server Name: 217.160.4.76

HTTP User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.202 Safari/535.1

unlink(/var/www/includes/tmp/cache/i18n.po/88c8bb3041dcc7bf05e823cd88a2b830.i18n): Permission denied

Error Type:   E_WARNING          

Source File: /var/www/includes/qcubed/_core/framework/QCache.class.php Line: 43        

Line 38:   

Line 39: // If Hash File doesn't exist or if the values don't match, delete and return

Line 40: $strHashFile = $this->GetFilePath() . '.hash';

Line 41: if (!file_exists($strHashFile) ||

Line 42: ($strHash != file_get_contents($strHashFile))) {

Line 43: unlink($this->GetFilePath());

Line 44: return false;

Line 45: }

Line 46: }

Line 47:   

Line 48: // If we're here, return the contents of the cache file

Call Stack:



#0 (): QcodoHandleError()

#1 /var/www/includes/qcubed/_core/framework/QCache.class.php(43): unlink()

#2 /var/www/includes/qcubed/_core/framework/QTranslationPoParser.class.php(33): QCache->GetData()

#3 /var/www/includes/qcubed/_core/framework/QTranslationPoParser.class.php(7): QTranslationPoParser::Load()

#4 (): QTranslationPoParser::Initialize()

#5 /var/www/includes/qcubed/_core/framework/QI18n.class.php(26): call_user_func_array()

#6 /var/www/includes/configuration/prepend.inc.php(131): QI18n::Initialize()

#7 /var/www/assets/_core/php/_devtools/config_checker.php(130): require()

#8 /var/www/assets/_core/php/_devtools/config_checker.php(6): ValidateInstall()

Variable Dump:   Show/Hide

Offline
Joined: 12/30/2009

We have found the error. To fix it we change the permissions to the files with chmod 777.

Anyway, thank you for the help jmirancid

jmirancid's picture
Offline
Joined: 04/04/2011

Hey Spike no problem, is good to know you have fix it =)

Is great have your solution in the forum for some other users experimenting the same issue.

By the way you put the chmod 777 permissions to all QCubed folder (your application included) and 777 is not to permisive to put in a site?

Cheers!!!

Offline
Joined: 12/30/2009

Yes, maybe it's too permisive but we had to find a solution, now that we know this change can make the site works or not we'll be putting different permissions until it has the best configuration to work.