I've copied a drupal6 site from a production server onto a dev server and have started trying to get it up and running and most of it runs ok except page variant.
On the live site the page variant shows on, on the dev site I can select the "Content" menu item and see all content that is supposed to be showing in the appropriate area however when It try to view on the front end on dev it shows the page wrapper but the main content area is blank.
When I click on the "Preview" menu item in the page variant admin the page doesn't display, however selecting this on the live server shows it fine.
It feels like a permissions / setting issue to me but so far I've not been able to figure it out. Any ideas?
This was a "Call-time pass-by-reference" issue and was caused by different PHP versions on live & dev. PHP 5.3 seems to allow the call allowed this call but gave a deprecation warning but the new dev server is on an updated version of PHP which doesn't allow this anymore (although it wasn't giving any errors either) so I had to make the following change (and will likely have several similar ones to do before I'm finished)
Had to update a function template_preprocess_panels_pane in in panels.module from
function template_preprocess_panels_pane($vars)
to
function template_preprocess_panels_pane(&$vars) {
as described in comment 21 on https://drupal.org/comment/6820396#comment-6820396
These was also a suggestion that you could update a php.ini value to allow call-time pass by reference (change allow_call_time_pass_reference = Off to allow_call_time_pass_reference = On in php.ini) but updating the code where necessary feels a better way to go.
Related
I'm using Joomla 3.8 to manage our community website (on the side pro bono). Everything was going well until I noticed an article with a padlock icon in the administration. I applied Global Check In, which unlocked the article. But now I find that I am unable to add or edit articles. Please see screenshot below:
The website is running on PHP version 5.6.31, with web server Apache.
How do I fix the problem? Is there any code I need to tweek?
This is how I determined the source of the problem. On the administration, I raised the error reporting to maximum:
Global Configuration > Server tab > Error Reporting (changed from System Default to Maximum)
I saw the following errors:
Notice: Undefined variable: plugin in */home5//public_html/plugins/system/connectdaily/connectdaily.php on line 42
Fatal error: Call to a member function logError() on null in /home5//public_html/plugins/system/connectdaily/connectdaily.php on line 42*
I deactivated the connectdaily plugin. The fix worked. I am now able to add and edit articles again.
I am still not sure where the connectdaily plugin is used for. If ever the website will need it, I will just reinstall the plugin.
Oracle 7
Nginx
PHP5.5
I am currently getting only a blank page when trying to access phpMyAdmin instance. I've already took look at the page source and there is HTML content but for whatever reason, the page remains blank. Is this a bug? Has anyone experienced this particular issue like this before?
http://pastebin.com/bDQ2p52b
I was finally able to resolve this issue by:
a) Enabling $cfg['AllowThirdPartyFraming'] = true;
b) Remove the hide class from libraries/plugins/auth/AuthenticationCookie.class.php on line 171
Although I recieved a login form, however it didn't resolve the underlying issue, as certian objects on the page were inoperable. Digging into the source page; I discoververed that js/get_scripts.js.php output was being trancuated. I did some researched online and landed on https://serverfault.com/questions/269173/why-is-the-response-truncated-at-16k-with-php-fastcgi, checked my fastcgi_temp_path and noticed that the ownership was set improperly on /var/lib/nginx/tmp. This resolved all the issues I was having earlier.
I have a problem with move site made in TYPO3 4.5.32 (with PHP 5.2.17) to another server (with PHP 5.4.25). When I login in BE everything works fine, but when I try to open site in FE I have blank Page without any source code.
I create blank page with basic TS:
page = PAGE
page {
10 = TEXT
10.value = Hello world!
}
with clear Setup, Constance and checked Rootlevel option I have blank page.
The response form server is: 200 OK
When I uncheck Rootlevel I have information no TypoScript template found.
Any idea what can be wrong?
A white page indicates that the script stops somewhere. I would check the memory settings in your php.ini. Set the memory_limit = 512M or take the same amount from the old server. If that not helped, you could turn on the PHP error log to see whats going on.
Try like this:
page = PAGE
page.10 = TEXT
page.10.value = Hello World
Here you can find a lot of nice information:
http://docs.typo3.org/typo3cms/GettingStartedTutorial/
Just to understand you correctly: You like to update a full blown 300 extension TYPO3 4.5.x installation to TYPO3 6.2 on a new server?
This is an important information because there are a lot of things which changed between these two versions. I really doubt that the majority of your extensions are ready for TYPO3 6.2.
In this case I would recommend to install a 6.2 version at your new server and rebuild the portal from scratch.
Is it way to deactivate all extension at a time (not one by one)?
After the update you already did, you should see a PackageStates.php file in /typo3conf/ folder. Copy it to somewhere else and delete it. TYPO3 should create a new one with only the basic extensions activated when you refresh the backend/frontend.
But as I told you above. I strongly recommend you the other way around. Built your portal up from scratch.
TL;DR : Upgraded PHP on our server which caused a bunch of Deprecated errors to appear in WordPress, tried a number of fixes but the errors won't go away.
PHP Version: 5.3.10
WordPress Version: 3.3.2
I have a WordPress installation that has been up and running for a little while now, with no complaint.
This week, we upgraded PHP on the server to 5.3.10, after the update, the WordPress Dashboard began filling up with errors like this:
Deprecated: Assigning the return value of new by reference is deprecated in /home/random/public_html/wp-includes/class-simplepie.php on line 738
A large number (I suspect 116) of errors like this (each on a different line) appear in
Incoming Links
WordPress Blog
Plugins
As advised by a number of posts around the WordPress forums, I disabled error reporting both at a file level (by adding error_reporting(0); to the top of wp-config.php and/or other files) and using PHP.ini. Phpinfo confirms that error_reporting = 0.
This had no effect, with the warnings still showing up on the dashboard.
I tried disabling all of my plugins and reverting to the default theme (with a mind to enable each one in turn to see if one of them was causing the issue) but the errors continued to appear.
Next, instead of treating the symptom, I went to see if I could fix the cause of the issue.
Getting deprecated error with Simplepie
and
Assigning the return value of new by reference is deprecated
pointed to class-simplepie.php having some out of date syntax inside.
Using find/replace in my text editor I swapped all 166 instances of
=& new
for
= new
And I am still seeing errors on my dashboard.
So, as far as I can see, there should be no errors to report, and if there were, they shouldn't be showing up anyway.
Wordpress is not running in debug mode.
A paste of my phpinfo can be found here: http://pastebin.com/Pk68sDL1 if it is of any use to anyone.
Not sure what to try next. Any tips much appreciated.
D
try this and u will not have this errors:
error_reporting(0);
ini_set("display_errors", "off");
ini_set("display_startup_errors", "off");
Or set the same directives in your php.ini file in your server.
I was having the exact same problem today and I also tried all of the solutions you listed. Eventually I realized that after I replaced
=& new
with
= new
in class-simplepie.php, I also needed to reload the modules in the dashboard. This doesn't seem to happen when you just refresh the browser page, or even hide the module and then show it again.
So I highlighted the Incoming Links module on the Dashboard and clicked Configure. I changed the RSS feed URL to anything else (google.com), hit Submit, and it worked. Refreshed that module with no more deprecated errors from class-simplepie.php. Did the same for the Wordpress Blog module and that also worked.
The only thing I cannot figure out is how to refresh the Plugins module. It doesn't have a Configure option and I can't get it to reload like the others.
Edit: Plugins module works now as well. Just needed time to reset.
I had these warnings as well. I stumbled across a message by a developer of simplepie that this happens with PHP5.3+ and is related to the compatibility to PHP4. Using simplepie v1.3-dev drops this downwards-compatibility and fixes that.
Download from GitHub
Add this to the top of your wp-config.php file, right after the first
error_reporting(0);
I am fairly new to creating websites and I have done a website that I did in a sandbox server on my personal computer, it works brilliantly, but as soon as I try to put it on my companies server to go up on the internet it doesn't work anymore. What the site does is it takes fields from an html form and then does a sql search of a database that I set up and works fine. Then after the user is done with the form they hit submit and the sql is run and results are returned to the same page. The form action="" and then the results are returned. I am not sure if the companies server has php installed, but I don't know if that would be a problem or not because the browser should still be able to display the php code. I have no problems with the html form, it is just when I hit submit that the page is returned and nothing is displayed.
Any help is welcome.
"I am not sure if the companies server has php installed, but I don't know if that would be a problem"
It is. Browsers can do nothing with PHP. Maybe you shoud register for a free hosting provider and learn the basics of hosting there.
PHP is a server-side language (i.e., it runs on the server, not the user's machine). Therefore, it must be installed on the company's server for any PHP code to execute properly. Browsers cannot interpret PHP code, and moreover PHP code is executed before the browser even receives any information (PHP: Hypertext Pre-Processor). Check that the server has PHP installed before you continue. (Also be aware of versions and features. For example, to use many new PHP features your server must be running PHP5.)
If you find that PHP is installed: Check your PHP syntax; make sure that no headers are sent after text is sent to the page; and make sure that there are no loops or anything in your code that could cause the script to continuously run without printing to the page.
Also, since your page is returned when you hit 'Submit,' but no new information is shown, make sure that there is not a problem with the MySQL configuration (e.g., incorrect password, query syntax, etc).
First you have to be sure that server has PHP installed.
make a file named phpinfo.php with this line
<?php phpinfo() ?>
and call it.
If it won't print out PHP config, you have to install PHP first.
Otherwise the problem most likely in the form of PHP tags, and you are using <? instead of <?php.
To solve, you can either change tags or set short_open_tag to on in the php.ini
According to your comment
when I hit submit that the page is returned and nothing is displayed
I am going to make an assumption that you are getting a blank page. If that is correct, then I am also going to follow that up with the assumption that PHP is installed, there is an error in your script (my guess is the database connection), and that the error is not being displayed.
Add these lines to the top of your page and post back with the result:
error_reporting(E_ALL);
ini_set('display_errors', '1');
Ya I think there is a problem in your database connection.First run your connect file whether it is showing some error or not.Plase add this line to your page:
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);
And please modify your php.ini file with this line:
display_errors = on