in wordpress, a valid callback for cp_admin_init and _canonical_charset - callback

I'm using WordPress 3.5 with child-theme of Twenty Eleven 1.5. Suddenly I'm getting following Warning,
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
I'm using following plugins:
download-manager 2.3.9
wordpress-seo 1.4.7
wp-pagenavi 2.83
Some more points:
1) If I'm giving mysite.com it's giving above 2 line warning. If I give www.mysite.com, the following line also include,
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-includes/pluggable.php on line 876
2) If I give mysite.com/wp-admin/ or www.mysite.com/wp-admin/, It's giving 1st warning and 3rd warning.
3) If I goto www.mysite.com/wp-login.php, It's giving following 5 warning.
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'cp_admin_init' was given in /home/templ/public_html/wp-includes/plugin.php on line 406
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, '_canonical_charset' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 368
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'wp_authenticate_spam_check' was given in /home/templ/public_html/wp-includes/plugin.php on line 173
4) If I give correct username and password, it's not going to login. giving following problem,
ERROR: Invalid username or incorrect password.
ERROR: Cookies are blocked or not supported by your browser. You must enable cookies to use WordPress.
I'm trying to find solution. I can't. Can any-one help me?

This sounds like a corrupted install. So you have a few options to fix this:
Attempt to get logins operational again and doing an upgrade though the wp-admin: Explained Below.
Do a manual Update: http://codex.wordpress.org/Updating_WordPress#Manual_Update
But First: Make a Backup
Please be sure to backup your install! Before proceeding: http://codex.wordpress.org/WordPress_Backups
Getting Logins Working: Masking the symptoms
First I would disable debugging output because that should fix most of these issues. When a warning occurs in Wordpress, PHP starts writing the response body and closes the header section of the response. This means that whenever Wordpress tries to add another header after the original warning was raised, PHP will raise another warning:
Warning: Cannot modify header information - headers already sent by (output started at /home/templ/public_html/wp-includes/plugin.php:406) in /home/templ/public_html/wp-login.php on line 380
So if we disable debugging then we should be able to mask the symptoms. This is a quick patch for a larger problem that we will have to solve with an in-place upgrade
To Disable Debugging
Ensure that the following constants exist and are set correctly is in your wp-config.php file
define('WP_DEBUG', false);
and
define('WP_DEBUG_DISPLAY', false);
Now you should be able to login to your site as an administrator without errors.
Disable your Plugins
Disable all your plugins in Plugins -> Installed Plugins This is imperative so that we can make sure that the update goes smoothly.
Do an Update
Go to Dashboard -> Updates and click either Update Now or Re-install Now
Reactivate your Plugins
Reactivate all your plugins in Plugins -> Installed Plugins and update them if necessary.
That's It
That's the process for reinstalling Wordpress. The key here is that you have Debugging enabled on a production site which is not good. You should always have WP_DEBUG and WP_DEBUG_DISPLAY set to false in a production environment.

Related

How to use custom dev-tool for Brave Browser?

I'm debugging wasm code in dev-tool, there is a line limit for displaying the wasm source code, which is 1000*1000 lines by default, when exceeds the limit, it shows ";; .... text is truncated due to the size":
My wasm is larger than that, so I'm trying to build my custom dev-tools. My environment is Kali Linux + Brave Browser.
According to this article, I commented out the lines:
And built successfully, the only difference is that the output directory in the article is ".../resources/inspector" and mine is ".../resources/inspector_overlay".
I tried launch it with --custom-devtools-frontend=file:///root/.../inspector_overlay, when press F12, the dev-tool fails to open, it shows error:
[82506:82549:0121/223355.672780:ERROR:devtools_ui_data_source.cc(306)] Failed to read /root/Downloads/devtools-frontend/out/Default/resources/inspector_overlay/devtools_app.html
[82506:82506:0121/223355.693282:ERROR:CONSOLE(67)] "Uncaught TypeError: Cannot read properties of undefined (reading 'setInspectedTabId')", source: devtools://devtools/bundled/devtools_compatibility.js (67)
How to make it work?
I found from this discuss that the correct path should be gen/front_end, so the param is: --custom-devtools-frontend=file:///root/Downloads/devtools-frontend/out/Default/gen/front_end

Commands invalid after 'import_board_preset' command

Currently I am trying to follow the MathWorks tutorial 1 to register a TE0720 with a TE0701-6 carrier board in Matlab. I followed the instructions, designed the block design and exported it as advised. Using the Matlab HDL Workflow Advisor I can follow unitl step 4.1 Create Project. Here, I get the following error message:
invalid command name "CONFIG.PCW_INCLUDE_ACP_TRANS_CHECK"
while executing
"CONFIG.PCW_INCLUDE_ACP_TRANS_CHECK {0} CONFIG.PCW_IOPLL_CTRL_FBDIV {30} CONFIG.PCW_IO_IO_PLL_FREQMHZ {1000.000} CONFIG.PCW_IRQ_F2P_INTR {1} CONFIG..."
(procedure "create_root_design" line 49)
invoked from within
"create_root_design """
(file "vivado_custom_block_design.tcl" line 986)
while executing
"source vivado_custom_block_design.tcl"
(file "vivado_create_prj.tcl" line 15)
This is regarding the exported block design in the corresponding *.tlc file.
After deleting the line mentioned in the error, the error persists, but for the following line. This holds true until I deleted all lines following
CONFIG.PCW_IMPORT_BOARD_PRESET {preset}
It seems to me that once the preset for the board is imported, all following commands are seen as invalid. If I put this line in the end of the list though, I get the error
ERROR [Common 17-69] Command failed: Missing name/value pair in -dict argument.
If I remove this line, I get the error
ERROR [BD 41-1811] The interconnect </axi_interconnect_0> is missing a valid master interface connection
ERROR [Common 17-39] 'validate_bd_design' failed due to earlier errors.
Is there a way to fix this or what is the problem here?
EDIT: I am using Vivado 2017.4 from the Vivado HL WebPACK. Could it be that there is a feature not available in this version for rebuilding the project as MATLAB intends to do?
EDIT 2: I started the complete tutorial fresh from scratch again and now I only get the error
ERROR: [BD 41-1811] The interconnect </axi_interconnect_0> is missing a valid master Interface connection
when going throught the HDL Workflow Advisor. As far as I understand the issue, Vivado searches for something to connect the axi_interconnect to. But isn't this the interface port (DUT) as described later in the tutorial (end of step 2 in Register the custom reference design in HDL Workflow Advisor, where the compiled simulink model should be connected?

Empty pagetree in TYPO3 7.2 backend

I am setting up a web portal using TYPO3 version 7.2. I successfully installed TYPO3 following this article on a Red Hat 4.8.2-16 machine. Everything worked fine and I created some pages until for some reason the pagetree didn't show any content any more. So now the backend looks like this http://goo.gl/3p0uQn
My browsers debug console only returns this error:
TypeError: TYPO3ViewportInstance.DebugConsole is null backend.php:79:5
but I have no idea if this is related to the empty pagetree.
This occurs on Firefox, Chrome and IE, so I guess it has nothing to do with the browser.
Also, I am logged in as an admin so it should not be due to wrong access rights.
Does anybody know what's going on there?
UPDATE:
The TYPO3 Log gives me some PHP Warnings
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Http/AjaxRequestHandler.php line 255
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Http/AjaxRequestHandler.php line 250
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Core/Bootstrap.php line 1193
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 439
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 438
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 425
Core: Error handler (BE): PHP Warning: Cannot modify header information - headers already sent in /var/www/typo3_src-7.2.0/typo3/sysext/core/Classes/Authentication/AbstractUserAuthentication.php line 424
UPDATE 2
Meanwhile I installed 7.2 completely fresh (even with a new database) and I still get an empty pagetree. I also tried 6.2 LTS, but also here, no pagetree. I'm beginning to think that there is a problem with my PHP settings. Im using PHP 5.6.9 and MariaDB 10.0.19.
Try tu put that on your php.ini :
always_populate_raw_post_data = -1
It worked for me.
Have a nice day.
Raf
You have a PHP error somewhere. Please check your webserver log or php log for error messages. You can also show the error messages by choosing the development preset in the Install Tool or by setting the context environment variable to Development.
Make sure to clear the cache via Install Tool at least once (Important Actions).

Warning: curl_setopt() [function.curl-setopt]: Invalid curl configuration option in facebook_base.php

A week ago I started to notice a problem with the php sdk file - facebook_base.php
sometimes when connected facebook member visit the site and the auto-login trigger I get 2 errors and sometimes only the first error (that is why I used it in my problem title)+ the site shows up but without showing that user is connected.
after a refresh no error is shown and the site for connected member shows up.
I've tried new version of php API and also old ones that worked and still problem remained.
any ideas what can cause the problem?
UPDATE: similar problem spotted here: https://developers.facebook.com/bugs/207087046099691?browse=search_512a0e37e7ecf6136191651
this is the errors:
Warning: curl_setopt() [function.curl-setopt]: Invalid curl configuration option in /home/admin/domains/mydomain.com/public_html/includes/base_facebook.php on line 970
Warning: curl_setopt_array() [function.curl-setopt-array]: Array keys must be CURLOPT constants or equivalent integer values in /home/admin/domains/mydomain.com/public_html/includes/base_facebook.php on line 946

Zend -> Warning: is_readable() [function.is-readable]: open_basedir restriction in effect

I am getting the following warning in my code:
Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(/usr/share/php/./views/helpers/Doctype.php) is not within the allowed path(s): (/var/www/virtual/example.com/:/usr/share/pear/) in /var/www/virtual/example.com/htdocs/rockhopper-v2/library/Zend/Loader.php on line 198
or
Warning: is_readable() [function.is-readable]: open_basedir restriction in effect. File(/usr/share/php//var/www/virtual/example.com/htdocs/rockhopper-v2/application/modules/default/views/helpers/Layout.php) is not within the allowed path(s): (/var/www/virtual/example.com/:/usr/share/pear/) in /var/www/virtual/example.com/htdocs/rockhopper-v2/library/Zend/Loader.php on line 198
what is the problem and will it cause problems in deployment and production stage of my application?
Thank you
This message appears because since Zend FW 1.10.1 the autoloader creates the path to those files differently. You can find some more information here: Zend FW Bug Report
To get rid of this message you can edit the file index.php and change the set_include_path to this:
set_include_path(
APPLICATION_PATH.'/../library'.PATH_SEPARATOR.
APPLICATION_PATH.'/../library/Zend'
);
open_basedir is set php is running in safe mode. It restricts you to the folders specified in the list. This might help: http://blog.php-security.org/archives/72-Open_basedir-confusion.html
And yes, you will need to change it on any server if you want to access files outside the default folder.