Magento white page at front and backend - php

After customizing some files last week, both the back end and front end of the site I’m developing for went blank. I have already searched the internet and tried out some possible solutions, but none of them works.
Somehow I can’t manage to show any error message. I already uncommented ini_set(’display_errors’, 1);, changed error_reporting(E_ALL | E_STRICT); into error_reporting(E_ALL); and I tried even more possible solutions.
I also edited the memory to 128M, changed some settings in php.ini, changed local.xml.sample to local.xml. Nothing seems to work.
I seriously have no idea how I can solve this, so that’s why I’m here. I hope someone can help me. If you need more information, please ask, I don’t really know what’s necessary to answer my question.
After adding the following lines to index.php I managed to get error messages:
error_reporting(E_ALL);
ini_set(’display_errors’, 1);
ini_set(‘memory_limit’, ’256M’);
The error I get is:
Cannot send headers; headers already sent in /home/cheapas/public_html/index.php, line 39
Trace:
#0 /home/cheapas/public_html/lib/Zend/Controller/Response/Abstract.php(115): Zend_Controller_Response_Abstract->canSendHeaders(true)
#1 /home/cheapas/public_html/app/code/core/Mage/Core/Model/App.php(1246): Zend_Controller_Response_Abstract->setHeader(’Content-Type’, ‘text/html; char...’)
#2 /home/cheapas/public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(80): Mage_Core_Model_App->getResponse()
#3 /home/cheapas/public_html/app/code/core/Mage/Core/Model/Url/Rewrite.php(204): Mage_Core_Controller_Varien_Front->getResponse()
#4 /home/cheapas/public_html/app/code/core/Mage/Core/Controller/Varien/Front.php(166): Mage_Core_Model_Url_Rewrite->rewrite()
#5 /home/cheapas/public_html/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#6 /home/cheapas/public_html/app/Mage.php(683): Mage_Core_Model_App->run(Array)
#7 /home/cheapas/public_html/index.php(91): Mage::run(’’, ‘store’)
#8 {main}
Guess what, line 39 is: ini_set(‘memory_limit’, ’256M’);
When I delete this line I get a blank page again, so that doesn’t solve anything. Does anyone have an idea on solving this? Thanks!
As you may have understood, I actually can get error messages to show when I force an error by adding an unknown or uncomplete line to my index.php. Somehow there is a problem which doesn’t want to show up.

Related

Fatal Error WordPress Custom Post Type UI + WPML

After updating the wp-core, wpml plugin the other language link stopped working, after this, we contacted the support, and tried to roll back everything, and nothing helps
We noticed the conflict between two plugins WPML and Custom Post Type UI.
We started getting this Fatal Error:
Fatal error: Uncaught ValueError: Missing format specifier at end of string in /home/itdspl/domains/itds.tld/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php:416 Stack trace: #0 /home/itdspl/domains/itds.tld/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php(416): sprintf('Nigdy wi\xC4\x99cej %', 'Case Study') #1 /home/itdspl/domains/itds.tld/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php(320): cptui_register_single_post_type(Array) #2 /home/itdspl/domains/itds.tld/public_html/wp-includes/class-wp-hook.php(308): cptui_create_custom_post_types('') #3 /home/itdspl/domains/itds.tld/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array) #4 /home/itdspl/domains/itds.tld/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #5 /home/itdspl/domains/itds.tld/public_html/wp-settings.php(617): do_action('init') #6 /home/itdspl/domains/itds.tld/public_html/wp-config.php(198): require_once('/home/itdspl/do...') #7 /home/itdspl/domains/itds.tld/public_html/wp-load.php(50): require_once('/home/itdspl/do...') #8 /home/itdspl/domains/itds.tld/public_html/wp-blog-header.php(13): require_once('/home/itdspl/do...') #9 /home/itdspl/domains/itds.tld/public_html/index.php(17): require('/home/itdspl/do...') #10 {main} thrown in /home/itdspl/domains/itds.tld/public_html/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 416
How it can be resolved? From where should I start or what to do?
What is an idiot minus to this question??? The problem was not in the plugin code!
After days of searching for the issue and talking to support, I found an issue in String Translation for plugins.
We haven't translated the Custom Post Type UI plugin, and we found that from 400 lines of strings only one was translated and it caused the issue.
No %s Found >>>> Nie %
So this % at the end of the string was the main problem. Obviously that this sign "%" it's incorrect for the code to be in the end. I don't know how that happened since we didn't do this, but probably some issues after updating.
So, be aware, that it could be a really small thing and actually not obvious to check. We searched really deeply since we couldn't see any fatal errors even with a debug mode.

Wordpress: Problem managin wp-users and the taxonomy.php file

I have a code to link our students users with the wp-user. It was working without problems, and creating wp users without problems, but between July 29th and June 2nd, I think some plugin have been updated and now I can't edit passwords or create useres from my php code. It looks like Wordpress is working fine but my code not.
require_once $_SERVER["DOCUMENT_ROOT"] . '/wp-load.php';
require_once $_SERVER["DOCUMENT_ROOT"] . '/wp-config.php';
require_once $_SERVER['DOCUMENT_ROOT'] . "/wp-includes/formatting.php";
require_once $_SERVER['DOCUMENT_ROOT'] . "/wp-includes/user.php";
wp_set_password($password, $id);
this code returns an error.
Fatal error: Uncaught Error: Call to a member function add_query_var() on string in /var/app/current/wordpress-beanstalk/wp-includes/class-wp-taxonomy.php:460
Stack trace:
#0 /var/.../wp-includes/taxonomy.php(441): WP_Taxonomy->add_rewrite_rules()
#1 /var/.../wp-includes/taxonomy.php(79): register_taxonomy('category', 'post', Array)
#2 /var/.../wp-settings.php(375): create_initial_taxonomies()
#3 /var/.../wp-config.php(36): require_once('/var/app/curren...')
#4 /var/.../api/wp.php(6): require_once('/var/app/curren...')
#5 /var/.../api/customers/changepassword.php(22): updateWpPassword('********', '3')
#6 {main} thrown in /var/app/current/wordpress-beanstalk/wp-includes/class-wp-taxonomy.php on line 460
Notice: is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/app/current/wordpress-beanstalk/wp-includes/functions.php on line 5313
Notice: is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /var/app/current/wordpress-beanstalk/wp-includes/functions.php on line 5313
I don't know what is happening, I have updated the plugins and the problem is there. I can't understand how Wordpress keep working but the code I have created calling to the wp function's is not.
The problem was related to $wp. I was overwriting that variable in mi code. The previous problem those days was a coincidence, something different and I was focusing in the wrong part of my code. Until I read the Chris Haas comentary I didn't realized that.

Podio PHP Issue

Hello Everyone and Podio Development team, I have some issues in podio since few days, I integrate podio in client project and project is in PHP Codeigniter, The podio API's were working before perfectly, but now there are some issues i am getting error The path '/item/basic' was not found.." Request URL: http://api.podio.com/item/basic
Although to verify code, I already checked old codes which was also integrated in podio and they are also not working now since few days. I checked podio website for Podio Items: Get item basic
https://developers.podio.com/doc/items/get-basic-item-61768
this is deprecated but no alternatives are provided and I am getting error regarding this.
When i comment code of podio and website works but when i uncomment code of podio and run it it shows error since few days, I have tried all steps and cross check in case code mistake there is no mistake as same code was working before, old codes also i checked which worked before not worked now. Kindly help me thank you.
Attaching screenshots
Fatal error: Uncaught PodioNotFoundError: "No matching operation could be found. The path '/item/basic' was not found.." Request URL: http://api.podio.com/item/basic Stack Trace: #0 /home/username/public_html/podio-php-4.3.0/lib/Podio.php(351): Podio::request('GET', '/item//basic', Array, Array) #1 /home/username/public_html/podio-php-4.3.0/models/PodioItem.php(120): Podio::get('/item//basic', Array) #2 /home/username/public_html/st_application/controllers/user.php(1459): PodioItem::get_basic(NULL) #3 /home/username/public_html/st_application/controllers/user.php(901): User->podioPropertyCreate(336, Array, Array, Array, Array, '3 Females, 1 Ma...', 'uploads/files/', Array, 'jahanzeb#gmail....') #4 [internal function]: User->add_property('add') #5 /home/username/public_html/st_system/core/CodeIgniter.php(360): call_user_func_array(Array, Array) #6 /home/username/public_html/index.php(202): require_once('/home
/username...') #7 {main} thrown in /home/username/public_html/podio-php-4.3.0/lib/Podio.php on line 324
This is the issue image:
You are not passing the item_id with the API call.
For PodioItem::get_basic API call, the item_id parameter (first parameter) is required one.
Also, please note that this get_basic operation is deprecated and will be removed soon.
Please use Podio Get Item API instead.

Gutenberg returns error 500 on save on certain pages

I have website which has Gutenberg and it is very important part of it, problem is..
When i enter page and try to save it i get error 500, in console i have this error in console
POST https://myDomain/wp-json/wp/v2/pages/5950 500 ()
POST https://myDomain/wp-admin/post.php?post=5950&action=edit&classic-editor=1&meta_box=1 500 ()
and this error in my error log
[12-Sep-2018 09:46:18 UTC] PHP Fatal error: Uncaught Exception: Invalid page template. in /usr/www/users/foodno/v32/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-duplication.class.php:99
Stack trace:
#0 /usr/www/users/myDomain/wp-content/plugins/sitepress-multilingual-cms/sitepress.class.php(4219): WPML_Post_Duplication->make_duplicate(5950, 'he')
#1 /usr/www/users/myDomain/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-synchronization.class.php(84): SitePress->make_duplicate(5950, 'he')
#2 /usr/www/users/myDomain/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-translation.class.php(248): WPML_Post_Synchronization->sync_with_duplicates(5950)
#3 /usr/www/users/myDomain/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-admin-post-actions.class.php(113): WPML_Post_Translation->after_save_post('535', Array, 'en', NULL)
#4 /usr/www/users/myDomain/wp-includes/class-wp-hook.php(288): WPML_Admin_Post_Actions->save_post_actions('5950', Objec in /usr/www/users/foodno/v32/wp-content/plugins/sitepress-multilingual-cms/inc/post-translation/wpml-post-duplication.class.php on line 99
I am also using WPML plugin, and on save plugin gets stuck screenshot
Loader is in loop...
Thing is, it saves the edited content, but still it returns error 500, i tried debugging and got absolutely nothing
I have googled it of course before asking and i found these as known Gutenberg issues that occured before... None of these did not help.. Does anyone have any suggestion or solution?
https://github.com/WordPress/gutenberg/issues/5675
https://github.com/WordPress/gutenberg/issues/8410
Thanks in advance
I asked on their git also, and i've got an answer from mr with nickname "brucepearson" and WPML will apparently fix this in next update, here is link to git q/a
https://github.com/WordPress/gutenberg/issues/9816

Magento Error: Headers already sent [duplicate]

This question already has answers here:
How to fix "Headers already sent" error in PHP
(11 answers)
Closed 9 years ago.
I got this error while adding products to the cart in my site:
Cannot send headers; headers already sent in /home/website/public_html/app/code/local/Perpetual/MultiAdd/controllers/Checkout/CartController.php, line 153
Trace:
#0 /home/website/public_html/lib/Zend/Controller/Response/Abstract.php(147): Zend_Controller_Response_Abstract->canSendHeaders(true)
#1 /home/website/public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(585): Zend_Controller_Response_Abstract->setRedirect('http://www.trum...')
#2 /home/website/public_html/app/code/core/Mage/Checkout/controllers/CartController.php(85): Mage_Core_Controller_Varien_Action->_redirect('checkout/cart')
#3 /home/website/public_html/app/code/local/Perpetual/MultiAdd/controllers/Checkout/CartController.php(203): Mage_Checkout_CartController->_goBack()
#4 /home/website/public_html/app/code/core/Mage/Core/Controller/Varien/Action.php(376): Perpetual_MultiAdd_Checkout_CartController->addmultipleAction()
#5 /home/website/public_html/app/code/core/Mage/Core/Controller/Varien/Router/Standard.php(248): Mage_Core_Controller_Varien_Action->dispatch('addmultiple')
#6 /home/website/public_html/app/Mage.php(459): Mage_Core_Controller_Varien_Front->dispatch()
#7 /home/website/public_html/wholesale/index.php(65): Mage::run('wholesale', 'website')
#8 {main}
Edit: Disabled extraneous plugin and that did not solve issue.
It appears that headers are sent in line #1 and attempted to be sent again in the file referenced in the error, CartController.php -
$url = $this->_getSession()->getRedirectUrl(true)
if ($url) {
$this->getResponse()->setRedirect($url);
} else {
$this->_redirectReferer(Mage::helper('checkout/cart')->getCartUrl());
}
Any ideas on how to stop Magento from sending headers before Mage does?
There should be a module settings file in app/etc/modules/ with a boolean in it. Disabling a module output doesn't disable the module. Only its output.
Removing the module from the community folder should do the job, but it could be dirty depending on whether this plugin has created tables on your database or not.
Suspicious module disabled?
Ok, let's go for another answer then.
First, check whether you get any output before the error stack trace. An output provokes the sending of headers for this output.
GO var/report and find out the problem file.
Check if there is any space before

Categories