I'm having this problem in my production server. I need to install my local copy of cakephp into a subdiorectory domain.com/cakephp, the I can see al it's contents correctly, the problem comes when the code requests for a controller/method using ajax. I believe this may have something to do with the .htacess, since I got this from javascript console in Chrome:
POST http://domain.com/clientes/lista_grid 404 (Not Found)
when it should be something like
POST http://domain.com/cakephp/clientes/lista_grid 404 (Not Found).
I've tried every possible .htaccess configuration for a cakephp subdirectory install. But no luck, I've got no idea what to do with this.
Related
I have a Laravel installation installed on https://dev.example.com for the purpose of staging and development before I move it to https://www.example.com.
The server is running NGINX and the Laravel installation worked just fine on my local machine. All links routed correctly and there were no problems.
Now on this subdomain, any inner webpage I try and access is coming back as a 404 error, even if Laravel was the one that generated the URL.
For example:
"https://dev.example.com" will load just fine but "https://dev.example.com/contact" or "https://dev.exmaple.com/testimonials" will return a 404 error even if Laravel was in charge of the URL generation.
Important to add that it seems the 404 error is coming from NGINX and not Laravel
When I look at the NGINx logs I see
" "/var/www/html/public/testimonials" failed (2: No such file or directory)"
Can anyone help?
I'm having issues with my Joomla installation.
It's a rather vanilla J! 2.5 (latest version) installation with K2 (I don't think it is related to my problem).
The problem is that any URL I make up (such as http://www.mysite.com/No-Such-URL-At-All) gives me the following error:
Error
Article not found
You are not authorised to view this resource.
I created an error.php file that should handle it in the template, but it is not used at all by Joomla, as I don't think it is really handled as error but as a permission redirection :\
So I tried adding this code to my template:
Code:
if (($this->error->code) == '404') {
header('Location: /404.html');
exit;
But no error was detected and the code was also ignored.
I inspected the response headers from the server, but I actually get a response 200, OK response :.
Some additional data that could be usefull
- It's hosted on a godaddy dedicated centos server
- SEF is enabled (problem continues also when disabled)
Let me know if any other information could help...
I really have no other direction I can think of, maybe someone has any idea why any 404 is turned into a permission redirection?
Check to see if when you have a 404 if Joomla is hitting the "com_content" component ( check the $_REQUEST variable). I had this problem and it turned out that it wasn't, it was hitting one of my custom components. If this is the case, here is what you need to do to fix it. For this example, lets say that its hitting 'com_home' instead of 'com_content'.
1). Copy components/com_content/router.php into components/com_home
2). Open components/com_home/router.php and replace all instances of "Content" with "home"
3). Open components/com_home/home.php and add the following lines near the top of the file:
JHtml::_('behavior.tabstate');
require_once JPATH_COMPONENT.'/helpers/route.php';
4). Copy the entire components/com_content/helpers into components/com_home
When that's done, the url mysite.com/does-not-exist should redirect to the error.php page you've set up in your template.
I've set up a Drupal 7 site locally and have ftp'd the site over to my ISP's server which is a linux box running PHP and MySQL.
I've never successfully logged into the site before and I have locked myself out. When I go http://www.example.com/?q=user and click on request New Password then I get this error:
Not Found
The requested URL /user/password was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
One thing I've been confused about and that is the .htaccess file. I never had one locally on my Mac and I did not need it (I know it is hidden) - so I downloaded one and deployed it to the web site but then I got 500 errors, it made it worse. I've since deleted that file and at least I get some content - but not very much - just the front page. I overrode the themes name in settings.php as I have user access errors there. I changed it back to one of the default themes and that allowed me to get some content and not the 'white screen of death'
Advice welcome!
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.
Okey guys i have my project deployed to a subdomain folder on my server and when I try to access that subdomain -> new.mysite.com code igniter loads the 404 not found page.
It works perfectly on localhost and on a server without subdomain for example mysite.com.
Any ideas? I tried to change the base_url to new.mysite.com and it doesnt work.
Is there a way to see what url it is realy trying to load I don't know. I'm desperate i guess i have to touch the routes but what to write there?
This probably hasn't got to do with your base_url setting. If your index page doesn't get loaded, something else is probably wrong.
Are you getting CodeIgniter's 404 message, or Apache's?
In case you're getting CodeIgniter's 404 message (even for your default index page), chances are CodeIgniter isn't able to parse the relevant URL section correctly. In that case: please check (or provide us with) your .htaccess file (in case you're using mod_rewrite).
On a personal note: I've experienced such problem before too. After much fiddling and cursing, I eventually decided to just dive into CodeIgniter's system files (I believe it was system/core/CodeIgniter.php) and to alter the piece of code that reads the relevant piece of the url.