In codeigniter I have using class name Login having controller file name login.php. It is working fine in localhost but when i am uploading it to the cpanel then it is showing 404 error. In that case we need to make the controller First letter Capital. Mean the controller name should be Login.php. Can you tell me the solution why it is working in localhost and not in cpanel. Because I have not seen this kind of rules in codeigniter user_documentation page.
It is in docs and reason for that is you are possibly using Windows in local development which is case insensitive meaning OS interprets lower and capital case equaly.
Related
Let's say I have some website with the name website.eu. When I deploy it and try to get access to a page online like this website.eu/about I catch the error:
"404 The page you're looking for could not be found. The resource that you are attempting to access does not exist or you don't have the necessary permissions to view it"
When I click on the link that brings me a website.eu/about it works well, but trying to type that URL in the input field it fails.
Everything works fine locally.
The project is developed using Vue3.
The project is no GitLab.
If someone helps I would appreciate it.
Hard to tell without seeing the code, but my guess is your router setup uses the web history mode, which relies on the server to have certain settings applied.
I believe switching to hash mode (while adding # to the routes) will work.
Alternatively, you can update your server to support redirects to have the html mode work.
example server configurations
This not a good day in IPP land. Spent the last 2 hours messing with an app that worked fine 5 minutes before that. I keep getting invalid token errors when I try to call the QB API.
I tried replacing the consumer key & secret with those from another app we have in development. Works great. The only difference I can see is that the working app has "localhost" set up as the Host Name Domain.
OK fine. Tried to change the domain to "localhost" on the failing app. No can do. You have to enter a valid domain name. Huh? Tried to change the app name on the app that works. Won't let me save the change because the domain name isn't valid.
It seems pretty clear that the Host Name Domain is the problem here, but why can't I use localhost in development, when I already have an existing app that does that.?
I should add that I'm currently using Intuit's sample web forms app as a wrapper for some code that I'm developing. It is that code that's throwing the exception, not mine. So the problem isn't in my code; it's got something to do with the way the app is set up # Intuit.
Please use a dummy host domain in development (e.g., example.com). This setting will not affect your development testing. We are working to clarify this in the documentation.
Are you using the dummy host name somewhere in your application? If not, then I'm not sure how it should affect the sample app settings. Can you verify if the app keys passed are correct in the web.config?
I'm using Pow.cx for local development servers - Rails, PHP and static. It's working fine locally, but when I try to use the new xip.io functionality to browse from another device I'm getting a different localhost site every time.
This particular incorrectly-served site is not set up in Pow, but I have an older virtual host set up for it.
Put another way:
stm.dev serves the correct site on my desktop.
stm.192.168.1.XXX.xip.io on my iPhone serves up a different site that is not configured in Pow.
I haven't been able to find any mention of a similar problem online, has anyone else come across this? This particular site is static html, if it matters.
So far I have been unable to get Pow to automatically pick up the xip.io addresses. However I did finally get it working to the point that I can continue building the site.
I followed the instructions from this link http://blogs.adobe.com/shadow/2012/06/19/shadow-xip-io-virtual-hosts-workflow-simplified/ in setting up a vhost alias for the site. I believe that cuts Pow out of the loop, but at least it's working now for testing on the other devices I need.
I would love to have Pow working as described, so if there are any suggestions on that end I'd love to hear it.
I need to use ZendAMF on a symfony project and I'm currently working on integrating the two.
I have a frontend app with two modules, one of which is 'gateway' - the AMF gateway. In my frontend app config, I have the following in the configure function:
// load symfony autoloading first
parent::initialize();
// Integrate Zend Framework
require_once('[MY PATH TO ZEND]\Loader.php');
spl_autoload_register(array('Zend_Loader', 'autoload'));
The executeIndex function my the gateway actions.class.php looks like this
// No Layout
$this->setLayout(false);
// Set MIME Type
$this->getResponse()->setContentType('application/x-amf; charset='.sfConfig::get('sf_charset'));
// Disable cause this is a non-html page
sfConfig::set('sf_web_debug', false);
// Create AMF Server
$server = new Zend_Amf_Server();
$server->setClass('MYCLASS');
echo $server->handle();
return sfView::NONE;
Now when I try to visit the url for the gateway module, or even the other module which was working perfectly fine until this attempt, I only see a blank screen, with not even the symfony dev bar loaded. Oddly enough, my symfony logs are not being updated as well, which suggests that Synfony is not even being 'reached'.
So presumably the error has something to do with Zend, but I have no idea how to figure out what the error could be. One thing I do know for sure is that this is not a file path error, because if I change the path in the following line (a part of frontendConfiguration as shown above), I get a Zend_Amf_Server not found error. So the path must be correct. Also if I comment out this very same line, the second module resumes to normality, and my gateway broadcasts a blank x-amf stream.
spl_autoload_register(array('Zend_Loader', 'autoload'));
Does anyone have any tips on how I could attach this problem?
Thanks
P.S. I'm currently running an older version of Zend, which is why I am using Zend_Loader instead of Zend_autoLoader (I think). But I've tried switching to the new lib, but the error still remains. So it's not a version problem as well.
got it...
I was not using
set_include_path()
while loading Zend. It's still odd that it would give such a cryptic error, but this was the missing piece indeed.
My website uses Response.Redirect("~/Main/Main.aspx") type redirects all over the place. Worked flawlessly until the Webhost4Life (don't groan) decided to migrate my website and in doing so managed to completely break it.
What is this "~" mechanism actually called?
Thanks, Rob.
PS. The bug is that Response.Redirect("~/main.aspx") from http://backdoor.whatpub.org/default.aspx doesn't go to http://backdoor.whatpub.org/main.aspx (as it did on the old server) but to http://backdoor.whatpub.org/live/main.aspx. Live is the name of the sub-folder containing the website and AFAIK means that the root is getting returned as http://backdoor.whatpub.org/live and not just http://backdoor.whatpub.org
it is a shortcut to HttpRuntime.AppDomainAppVirtualPath property, which refers to the virtual application root, not the root of the web server.