I am also trying to deploy a ZendSkeletonApplication on a shared host but I am facing some problem regarding redirection. The problem is when a user try to login it gets stuck to /projectname/user/authenticate. It doesn't get redirected to dashboard after authentication.Unfortunately all i see is a white, empty page. Locally it worked perfectly Here it looks like Zend doesn't recognize that it should do anything with this url and redirecto to appropriate action.
Thanks in advance
The problem is presented by the new release of PHP. Try updating your version of php above 3.xx. I upgraded to the latest version of php in the hosting and the problem was solved. PHP 5
Related
I can't access my prestashop admin page (in localhost)?
When I enter into this page, it's shows this error!
How to fix this problem? Please help me.
Prestashop changes its admin folder to something like admin12fsg7wghdfgf. You need to go to folder where you installed prestashop and find that folder. And after that you could enter backend side by link similar to this http://localhost/prestashop/adminwt3452sdg
I had the same problem.
I even deactivate the antivirus and nothing fixed the problem.
Then what I did is to install the eCommerce in a Cpanel and over there all worked perfectly.
It's caused perhaps because Prestashop is tracking urls for his product's installations and of course this doesn't work in localhost...
I had a problem and it became alright after I downgraded the PHP version to the one recommended by Prestashop for the relevant version.
In my case, the PHP version was 7.2 and Prestashop 1.6. The admin page did not open, 500 Error.
I lowered the PHP version to 5.6. May be upto 7.0 it accepts.
I've installed the community version of DNN.
then i've started to develop some modules - this worked fine.
then i saw that dnn have AuthenticationServices and wanted to create one for connection to MS CRM.
then i've tried to install this AuthenticationServices and it worked. After that i wasn't able to login to the host anymore. i keep getting the error: ERR_TOO_MANY_REDIRECTS.
bevor i've started with changes i cloud login with dnndev.me/admin or dnndev.me/host.
dnndev.me/admin get redirected to my custom login page.
And dnndev.me/host gets me an ERR_TOO_MANY_REDIRECTS error.
is there an easy way to repair this? or do you prefer to reinstall dnn?
It looks like when you try to login into DotNetNuke it will add the login module to the home/start site into the ContentPane.
Unfortunately i changed the template, with one that didn't have the ContentPane. So you can't access with the link dnndev.me/admin.
For access via dnndev.me/host, I'm not quite sure if it was the same problem.
I solved everything with a new clean install.
and a little hint:
i'm now create a master login page like masterlogin and put the account login module on it.
now i should be able to login whenever an error occur.
Basically for a Facebook tab I have a PHP app and want Heroku to use the 'public' folder as the web server's root folder instead of pointing to the very root of the app. Any help would be awesome as it seems Heroku doesn't have a ton of documentation around it's config options. Thank you.
I hosted my php codeigniter project on heroku lastmonth, so unless there is a server side configuration needed for your project. You should be able to host your zend project by pushing it as git repository to heroku. Just follow these tutorials.
http://www.youtube.com/watch?v=L2YlEIMrGxA
https://devcenter.heroku.com/articles/facebook
Not sure of that but Heroku's website says "Agile deployment for Ruby, Node.js, Clojure, Java, Python, and Scala.". But since there's no mention of PHP I think you can't deploy your Zend app on Heroku.
EDIT : my assertion was false, see comments
Thats not entirely correct (or no longer correct) - if you put a repository with an index.php in the root up it seems to recognise that as a php app.
The answer is not yet at least. They only offer the Facebook app hosting. I have gone with PHPFog for quick PHP hosting now.
EDIT: PHPFog is no more, now they have AppFog.
Hey I created a default MVC2 project just to see if i could get it to run on my site hosted by MochaHost. Unfortunately it doesn't seem to display the page instead it just displays the directory.
Has anybody had this problem before? Or know of a tutorial that may help?
Did you confirm with MochaHost if they are running on IIS6? I suggest open a ticket with them and understand what they have in the environment.
Here is a tutorial for deploying MVC with IIS6: http://blog.stevensanderson.com/2008/07/04/options-for-deploying-aspnet-mvc-to-iis-6/
You can also try disabling the directory browsing so that you know if there is a real problem.
I have a DNN site (5.06) that I developed on a standalone machine running IIS7. When I copied the site to the production machine running IIS6 and enter the URL, such as www.site.com, I get a generic DNN error page with no additional information. However, if I add the default page, www.site.com/Default.aspx everything works fine.
The Friendly URL settings were never changed and I've verified Default.aspx is entered on the Documents tab in IIS6. The portal event viewer has no entry for the error page I get.
I'm nearly certain it has to do with migrating from IIS7 to II6; clearly I'm missing something here. Any ideas?
DNN has confirmed this is an error in 5.06, and will be addressed in a future update. That doesn't help me today, but I was able to work around the problem by adding the following to the Friendly URLs list:
Look for: .*/
Send To: ~/Default.aspx
I can't find the forum thread I was reading yesterday, but did find this one which also goes into detail on the issue: Error upgrading from 5.5.1 to 5.6.0
Pretty odd...
Double check PortalAlias table in your SQL server. Confirm www.site.com is in there.
Double check host headers in IIS6 has www.site.com
Make sure Default.aspx is in the documents area of IIS6 and set as the top default to run
Recycle your app pool
cross your fingers
Only thing I ever run into from IIS6 and IIS7 is in the app pool running in Integrated mode or classic... but that is usually as issue going from IIS6 to 7, not vice versa.
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have the correct machine key and connection strings. This is my last resort when DotNetNuke is being strange. I am running 10+ DNN sites at version 5.6.0 and I only encountered this issue once.