When I go open up my Codeigniter website on my localhost using Wamp and XAMPP, both works. But when I move it to Ubuntu on Google Cloud, it only works for the first page, afterward, it shows the error when going to another page.
I'm using:
Codeigniter ver 3
Apache2
php7.3
Does anyone know what might have caused this?
Other Pages
It would be ideal if you check first the class name and the record name that both should be title case (start with a capital letter).
So if the class name is 'controller.php', the file name needs to be 'Controller.php', otherwise, CodeIgniter will throw a 404 error.
In localhost it probably won't be obligatory, yet in server it will check every one of these standards, else it can't distinguish the correct class name.
Related
I am having trouble getting a project to work that I have inherited and not setup myself. I install the DB and make sure the file/folder permissions are correct -- but I am getting this error when I try to get to the local site -
This domain is not set up correctly. Please go to http://localhost/myproject/sites and log in to add this site.
I get that error again when I go to that URL... so not exactly helpful on 'adding sites'.
Is there any way to setup a local site in the database manually without using the installer?
Check the field "domain" in the table "core_sites" in your PyroCMS DB.
This field should be set to the domain you're open the website on.
This is usually caused if you're installing PyroCMS through a different URL, than you use to open the website.
e. g.
install through http://dev-server/website/pyrocms/installer, but call the website on http://pyrodev.local because you've set up a virtual host and corresponding DNS entries.
I have a web application hosted on AWS on Ubuntu server. I have Apache and mysql running on it. It was working perfectly fine till yesterday, All of sudden when I try to access phpmyadmin using my domain name (like http://example.com/phpmyadmin) it gives 404 error.
If I simply type http://example.com on the browser it opens the home page, but if I click on any of the link of my site which refer to different directory, gives the same error.
I have checked the 000-default file under /etc/apache2/sites-enable. My Document Root is set perfectly fine, and directory has Override option to All.
Can any one have any idea then please help me.
Thanks
I am developing a joomla component in my localhost, every thing is ok on the localhost but when i create installation package and install the component on the online host i get 500 view not found error
PS. I added all view files in the package also added views folder to installation xml file
also i checked files in the host , every needed file exists and there is no missing file.
another thing that i should say is that im running joomla 3.3.0 in localhost but 3.3.3 in online host.
I read all "view not found" articles in the internet :D but i couldn't find a solution :(
Regards
Edit :
i uninstalled the component from localhost and installed component package on it again , every thing works fine , so the error is on the host. i changed files permission but still have same error.
It's not a permissions issue at all. Joomla simply can't find the view with given name. Check your view name VERY carefully. It should be MyComponentViewMyPage, not myComponentViewmyPage or MycomponentViewMypage. Joomla is damn sensitive to this stuff.
Here's an example:
class SmartShoutboxViewShout extends JViewLegacy
Smart Shoutbox is the name of the component and Shout is a page it belongs.
Joomla can't find the view with the given name. Besides #TheKrotek considerations, you should check the filename capitalization. Windows, for some wild reason, cannot tell "a" from "A" in a filename.
I recently moved a magento install to a new server and a new domain. I updated all the entries in the database with the new domain and path. The admin works fine, indexing works fine, cache management works fine.
However on the front end, the site renders all the way until the first product, and then it stops. The rest of the products don't render, and neither does the footer or any other blocks.
I tried to switch back to the vanilla theme that magento ships with, and it still happens.
The files on the new server are exactly the same (rsynced), and the only difference in the db is the domain and path.
Any ideas?
Edit
If it helps, the currently broken url is http://stiles-store.ddmstaging.com/
It's a fatal error. Turn on developer mode and reload the page - you will see the error message.
You can turn on developer mode by two ways:
1. At backend
2. Change code in index.php from
if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
}
to
//if (isset($_SERVER['MAGE_IS_DEVELOPER_MODE'])) {
Mage::setIsDeveloperMode(true);
//}
This error is occurring because you might have specified some images or links of your development machine. So Magento is not able to connect to your local machine/development machine from where it is trying to fetch the components.
Try to check whether you have specified the links of your server on which you are currently running your magento instance .
Hope this helps you
Missing GD support in PHP is the reason for this.
In our case GD support was compiled into PHP 5.3, but when we migrated to the new server with PHP 5.4 the sysadmin forgot to include the now shared GD module.
Unfortunately there were no error messages in the server and Magento logs. Basically this question resp. Jack's last comment saved me a ton of time!
Hope this will help others, as I was searching for the PHP version and product image URLs not rendering.
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.