CI-HMVC-Doctrine routing error in Unix Server - php

I just finished testing the website on Windows server. The whole website was being made and tested in Windows environment. Everything is working fine but as I launch the website to a server with UNIX environment, I am getting the following error.
http://wevte.com/test/
Unable to load your default controller. Please make sure the controller specified in your Routes.php file is valid.

Solved the issue by chainging the controller file name as home_Controller from Home_Controller..

Related

Laravel 5.2 - Staging to Live Server : 500 Internal Server Error

I have a Laravel 5.2 project working fine locally, after uploading to a live server I have a 'laravel' folder in my root directory and public folder under 'public_html/testsite'
My 'index.php' points to the correct '/bootstrap/autoload.php' and '/bootstrap/app.php'
Upon going to my 'url/testsite/' I get a blank page only (was working fine L5.0) firebug shows : 500 Internal Server Error with HTML : Reload the page to get source for...
index.php is loading by testing with die() before any 'require' methods, but after 'require... autoload.php' the die() is not working, however it is successfully calling autoload.php as a die() works within this file.
I'm not sure if this is a .htaccess issue, or maybe I had to set something up in cPanel last time for this folder (I can't remember). I'd appreciate any help!
Please note this Laravel project sits as a test site in a /testsite/ folder along with my current live site files.
Amongst changing many things at once, I appeared to have solved this by setting up a subdomain within cPanel and setting this to my testsite/ folder.
This was on a server with my current website live under public_html/ and setting up a test laravel app(website) with under public_html/testsite/ to work as an independent site for testing.
The typical "change permissions on storage folder" suggested elsewhere on stackoverflow did not solve my issue so hopefully this helps someone in the same boat.

how to Load Helpers in Codeigniter on Linux machine?

i was working on Codeigniter Application in WAMP and then i had to move my project to a LINUX machine.
Now When i have installed LAMP there. but When i try to access my application i get an error:
An Error Was Encountered
Unable to load the requested file: helpers/url_helper.php
i checked my autoload.php. This worked on my windows don't why its not working here.
$autoload['helper'] = array('url','html','crm_helper','form');
Can you please guide me where i am going wrong?
From your modified question, it seems that you are in fact missing the url_helper in your autoload line. It should be like this:
$autoload['helper'] = array('url','html','url_helper','form');
Also include the exact version of codeigniter that you've installed, in your question.
This happened to me ! on my local windows system it was fine ,but when i migrated to Linux server (my hosting server )then it generate the same error: it was due to case-sensitivity of Linux.
these are two deffrent words in linux:
'crm_helper'
'Crm_helper'
so i suggest you to check your files name ,
Linux system crm_helper and Crm_helper are two different files.
remove _helper while loading any helper file / code

Invalid request error in symfony on Linux server

I have developed i web application in symfoy2, my development environment is Windows (using wamp server), but when deployed it on a Linux server, there is a page which gives me the "invalid request" error, i checked the URL and Parameters, also the query, everything were the same, it works in windows but not in Linux. is there any case sensitive problem? or variable naming and parameters?
The problem was Case Sensitivity, My controller was named like viewSalarayTEmplate.php but the link to this file were specified like: click to view then i change my code to : click to view i found the problem after i checked the error log file and it was "the directory is not exist".

CodeIgniter giving 404 on a webserver

I loaded my codeigniter site onto my actual webserver (instead of just local). I am getting a 404 page not found even from the root domain. On my localhost it works fine.
Try going to searchnwork.com and it gives the Codeigniter 404. How can I start debugging this and seeing what page CodeIgniter thinks it's loading?
Go to config file and check the base_url setting
or add this
$config['base_url']='http://searchnwork.com';
Look into /application/logs/ folder (this catalog must be writable to logs could be written). Check if you have model and controllers names in lowercase - it's common problem especially if you've moved site from Windows server.
do you have access to the PHP log and Apache log - check if its firing errors on both ends.

PHP CodeIgniter 404 on deploy

Oooops I did it again.
My site worked perfectly locally
My development machine is a windows WAMP2 setup
My server is a CentOS 5.5 APACHE 2.2 PHP5 seup
I'm getting a 404 on the codeigniter site that I've deployed, and I really can't make out what's wrong, so please help me find the error.
It's the root url. I haven't set up dns so it's just the ip address of the server. It was showing the standard apache page before I uploaded codeigniter. I've looked over the config file, and it looks ok. Could it be a file permissions error? i have set chmod o+rw in the whole /var/www/html dir. the error_log in the httpd shows nothing
I've tried testing if it was the mod_rewrite module, but I created a test directory with a .htaccess file with RewriteEngine ON that didn't give me an error, so that can't be it.
In codeigniter I've set the log_threshold to 4 in the config, but I don't get any log messages, so I can't really make out if it's a pre-> codeigniter error, but I really don't think it is, as it's loading my Error view, still Why isn't there any log being written, what's it about?
Any help would be extremely appreciated as I'm running on fumes to get this working...
Update
Thanks to #jondavidjohn I have discovered that hitting the controller directly IE:
http://addr/index.php/GeoController/markers/
Will provide me with a controller specific error saying:
unable to locate your model "modelname"
SOLVED
Thanks to #jondavidjohn, and #timdream for giving me the clues to solve this one. It was a naming problem, I had filenames that were camelcased, and they can only be small from what I understand now, so the ROUTE was innefective in that it lead to Site, but should've lead to site although I had a Site.php I had to change it and the route to site.php
make sure you have the correct settings in system/application/config/config.php.. pay special attention to
$config['base_url'] = "http://www.example.com";
Make sure you are putting in the root domain of your site, also check your routing config and make sure you have the correct default controller set in system/application/config/routes.php
I recently started using a fresh install of codeignitor 3.0 and had no problems on my dev server (Windows) then when I moved to my live server (Linux) I started getting a 404 error.
The reason for this is that in 3.0 you are meant to capitalise the first letter of your controllers/models and also the file name.
e.g.
class Test_model extends CI_Model {
Test_model.php
Hope this helps some people who end up here!
For reference:
http://www.codeigniter.com/userguide3/installation/upgrade_300.html
$config['uri_protocol'] could also play a part. It's default to AUTO, which looks for environment variable that contains the actual URL automatically.
I had a web app that fails when I switch to php-cgi from mod_php for my server. Changing the config to REQUEST_URI solves the issue. I found the valve by digging phpinfo() outputs, you could try to do that.
My first bet is that you were developing this and modified the .htaccess file.
HOWEVER, if you went from a Windows -> Linux system change (dev on Win, prod on nix) then you have to keep the Controller names in mind, if a file on windows was "Home.php", and you used "home.php" in the config as your default route, then it will fail.. as there is no "home.php" file.
Home.php != home.php
Linux is case sensitive. Check that out, it might be a simple thing but could cause snags.
Again I am just guessing due to lack of details.

Categories