Now, I'm not exactly and expert in PHP, but my CMS i've created is going very well on my local server. I've attempted to place it on a live server to get blank page outputs everywhere except from when i use Codeigniters 'welcome' controller. Now i've checked every single file and i don't have one page that i close the PHP tags like so ?> when the page is completely PHP.
So is there a way that white space could be doing this another way apart from white space after tags?
Does white space after php tags between HTML tags count?
I've tested my database configuration and it works perfectly, so i don't know what else it could be. Just getting fed up of looking for something i'm completely not sure about and getting no where.
EDIT: You can see my lovely whiteboard here: http://asphaltcms.com/
EDIT: I can 100% confirm that preset/new controllers, models and views are working so it's something wrong with my current controllers ect, can white space appear in more than just after and before <?php ?> tags?
Thanks for reading.
I'll recomended to check following points if you are getting white screen ,
1:Check logs (PHP,Apache both)
2:Compare PHP info with your local code to live.
3:Check if short_open_tag is on or not
4:Enable error in config file.(error_reporting(E_ALL);
I hope this would help you to get rid of white board :)
Well i never figured this out, but my working result was just new codeigniter installation and re writing the code out quickly. Works on 3 web servers without any issues.
I later encountered an issue with .htaccess files being involved but i've resolved that :)
Thanks for the help.
I've just moved a site to a new host/server and experienced the same issue - White screen and no errors.
I noticed that I didn't have the php module GD or MYSQL installed so I installed those and it fixed my issue.
On ubuntu:
sudo apt-get install php5-mysql
sudo apt-get install php5-gd
Related
Firstly I know how to deploy and work with files, I don't need answers saying 'redeploy static content' or 'clean cache' - experience from the research.
We having an issue on our development server. We have tested it with multiple projects, versions vary from 2.1.5 to the 2.2.3 open source.
After steps below we are receiving random 400 errors on some files (1-10 files). All those files are .js.
FUN PART:
After trying to get that file again (open in new tab) - everything is working fine, file is there, nothing bad.
After trying hard refresh again - again errors, but on other files.
After multiple soft refreshes (F5) - it looks good again.
Deployment mode - Developer
Steps to reproduce
Install Magento without Sample date (tested with 2.2.3) - nothing configured.
Set deployment mode Developer
Deploy static content or just clean /pub/static/
Chrome/Firefox - Inspector->Network tab->Disable cache (CHECKED)
Clear site data on the browser.
Create a product - for testing.
Go to the website and then to the product (no errors even after hard refresh).
Add product to the cart. (no errors even after hard refresh).
Go for example to the category. (errors even after hard refresh).
After clearing site data - everything looks fine again.
We have reproduced this on multiple pc's / webbrowsers.
Server info:
PHP: 7.1.16
APACHE: 2.4.33
DirectAdmin 1.52.0
Debian: 8
Any suggestion what to do or what to check/change will be useful (except a stupid ones, no one likes those)
P.S. I was not sure if I should post it here or magento.stackexchange.com
Or if I can post on both websites at the same time.
Good morning all
After all we have found an issue. It was an apache module : mod_ruid2
After it was disabled - no more random 400 errors has appeared.
I hope this anwer will help someone even if this is an uncommon issue.
To turn the module off, you need to do the following steps in the command line:
cd /usr/local/directadmin/custombuild
./build set mod_ruid2 no
./build apache
I've been working on setting up correctly my xdebug debugger so I can improve my soft dev process, I manage to get xdebug working with phpstorm for some files that are outside of the project as in the first picture. But when it comes to debug some of the files that are inside of my mvc project (my app folder) I can set my debbuger to work properly and as far as now Im kind of stuck so any help would be welcome.
When I debbug phptest.php it work perfectly because it's an easy mapping
But when I need to debbug something like any php script on my controller folder for example, I can't get to there.
So please any ideas on how to do this.
Regards
Added a new screen shot of my mappings settings as #rafail pointed :)
For further or similar problems, my error was that i added index.php to my excluded paths and because of that I was never be able to debug, I deleted it and now it works fine.
especial thanks to Rafail Akhmetshin for his patience help.
Resume:
Check for exclude paths
Start debugging with phpStorm button
Make sure you are listening on the port
as a note point
make sure to check/uncheck
break at first line on php code
and break on first line when no mapping
I am using XAMPP server and want to install magento framework. However while installing after filling up the configuration page and clicking continue the page is reloading and a blank page is coming. Tell me how to fix this?
Probably you have not set the pre-configuration settings correctly. Try with a clean install following any of these tutorials: this, or this (second one is easier and more descriptive) and make sure you have done all pre-configurations correctly. Furthermore never forget to check the logs. Most of the times for blank pages there are pretty good answers in log files ;)
I started using PEAR yesterday, but Im having trouble.
When I launch the app, there is a bunch of QuickForm code at the tom of the page before the app.
I have followed the installation instructions from pear to the word.
Downloaded packages (including QuickForms), added the the path variables.
But for some reason it does this. I can not paste the code here as it is quite broken up into a lot of files. But maybe someone has come across something like this before.
You have set PEAR DB's debug level to non-zero value.
Set it to:
DB_DataObject::debugLevel(0);
Reference:
http://pear.php.net/manual/en/package.database.db-dataobject.db-dataobject.debuglevel.php
I have been developing a Wordpress site locally using MAMP, and I have run into an issue twice now where when I leave at night and come back, I can't access the admin page. I have debugging on, and there aren't any fatal errors. I can access the front-end of the site just fine, but I can't log into the admin page. All I get is a white screen like:
Here is the front end:
As you can see the front end is working well, but I can't get into the admin section. I've tried to re-login and it just doesn't work.
What could be causing this? The last time this happened, I had to reinstall the entire site. I really don't want to do this every day. I know that everything was working when I left, and I haven't made any changes today.
I just ran into a problem with a brand new MAMP install along with a fresh WordPress install, with current files downloaded on 2020-06-08. MAMP installed perfectly. WordPress also installed perfectly, and the default website was accessible on my localhost. When I tried to login to wp-admin, however, I kept getting prompted to enter my username and password with no errors.
I followed every "fix" I could find and none of them worked. I uninstalled and reinstalled everything, created new databases, etc. multiple times with the same results.
After nearly 48 hours, I looked at MAMP preferences and went to the PHP tab and noticed there are two versions (7.3.9 and 7.4.2). I switched to 7.3.9 and I was able to login.
It looks like one of your plugins may be causing some trouble, as per this line:
Warning opendir(/Applications/MAMP/htdocs/wordpress/wp-content/plugins/tmm_shortcodes/views/.DS_Store/popups/): failed to open dir: Not a directory in /Applications/MAMP/htdocs/wordpress/wp-content/plugins/tmm_shortcodes/index.php on line 148
Try disabling the plugin through your PHPMyAdmin and try loading the admin page again. You should be able to find the list of active plugins in the wp_options table under
active_plugins. Make sure to save a copy of the contents of that field in a text file, in case something goes wrong so you can reset it to the original parameter.
I understand this is a very old post, but had this problem recently.
Found that my wp-config-sample.php file was missing a closing php tag ?>. Amended that and the login worked fine.
Thought I'd add my experience here. Might help someone down the line!