420DankStank
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Theme ErrorsI’m aware that my theme is out of date. I’ve commented on the authors theme site, to see if he will be updating the Theme. No reply yet.
I didn’t want to switch themes b/c a lot of my website is hard written into the theme… Or so I am told.
If I change themes, it doesn’t display my site properly, so I will have to start all over. That is going to be my last option.
I turned off all my plugins by renaming the folder. Then I just deleted the wp-admin folder, and wp-includes folder. Re-installed the two folders + the loose files in the htdocs folder from a fresh WP download.
The site is now giving me a different error: PHP Fatal error: Call to undefined function add_filter() in /usr/home/wash20/www/htdocs/wp-includes/shortcodes.php on line 334
Still can’t log into my dashboard. If I go to my backend login page, it takes me to a 404 page on my website.
Forum: Hacks
In reply to: Custom Plugin Fatal errorsNow all of my errors are gone from my page, but I still can’t get my plugin to work. I’m going to do a some research and update later.
Forum: Fixing WordPress
In reply to: An Unexpected HTTP Error – to be fixedYou have an old plugin or theme or both. I’m having the same problems. You can see some of my fixes on http://wordpress.org/support/topic/custom-plugin-fatal-errors?replies=12
Forum: Hacks
In reply to: Custom Plugin Fatal errorsAlright! Error Warning: Warning: Missing argument 3 for wp_register_sidebar_widget(), called in /usr/home/wash20/www/htdocs/wp-content/themes/connections-reloaded/functions.php on line 151 and defined in /usr/home/wash20/www/htdocs/wp-includes/widgets.php on line 604
I fixed the error by going to the widgets.php and checking out line 604. It says it wanted to see: $wp_register_sidebar_widget
So, on my theme function.php near line 151, i changed:
if ( function_exists(‘wp_register_sidebar_widget’)
to:
if ( function_exists(‘$wp_register_sidebar_widget’)Error gone.
Forum: Hacks
In reply to: Custom Plugin Fatal errorsSo on my Shortcode.php, near line 174, I had:
wp_deregister_script('jquery'); //deregister current jquery wp_register_script('jquery', 'http://ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.js', false, '1.6', false);I changed it to: `function pubverify_enqueue_scripts() {
wp_deregister_script(‘jquery’); //deregister current jquery
wp_register_script(‘jquery’, ‘http://ajax.googleapis.com/ajax/libs/jquery/1.6/jquery.js’, false, ‘1.6’, false);
wp_enqueue_script(‘jquery’);
}`That took care of my error:
Notice: wp_deregister_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /usr/home/wash20/www/htdocs/wp-includes/functions.php on line 3587Forum: Hacks
In reply to: Custom Plugin Fatal errorsUpdates:
To show me what was being called wrong, I entered
throw(new Exception('Testing')); // line added to force an exception <<<<<<<<<<<<<<<<<<onto my functions.php on line 3585// Allow plugin to filter the output error trigger if ( WP_DEBUG && apply_filters( 'doing_it_wrong_trigger_error', true ) ) { throw(new Exception('Testing')); // line added to force an exception <<<<<<<<<<<<<<<<<< $version = is_null( $version ) ? '' : sprintf( __( '(This message was added in version %s.)' ), $version ); $message .= ' ' . __( 'Please see <a href="http://codex.wordpress.org/Debugging_in_WordPress">Debugging in WordPress</a> for more information.' ); trigger_error( sprintf( __( '%1$s was called <strong>incorrectly</strong>. %2$s %3$s' ), $function, $message, $version ) ); }That forced a new error in DEBUG mode:
Fatal error: Uncaught exception 'Exception' with message 'Testing' in /usr/home/wash20/www/htdocs/wp-includes/functions.php:3585 Stack trace: #0 /usr/home/wash20/www/htdocs/wp-includes/functions.wp-scripts.php(110): _doing_it_wrong('wp_deregister_s...', 'Scripts and sty...', '3.3') #1 /usr/home/wash20/www/htdocs/wp-content/plugins/mmjverify_shortcode/mmjverify_shortcode.php(174): wp_deregister_script('jquery') #2 /usr/home/wash20/www/htdocs/wp-settings.php(196): include_once('/usr/home/wash2...') #3 /usr/home/wash20/www/htdocs/wp-config.php(90): require_once('/usr/home/wash2...') #4 /usr/home/wash20/www/htdocs/wp-load.php(29): require_once('/usr/home/wash2...') #5 /usr/home/wash20/www/htdocs/wp-blog-header.php(12): require_once('/usr/home/wash2...') #6 /usr/home/wash20/www/htdocs/index.php(17): require('/usr/home/wash2...') #7 {main} thrown in /usr/home/wash20/www/htdocs/wp-includes/functions.php on line 3585It seems that in my plugin “MMJVERIFY_SHORTCODE” I have a deregister problem being called on line 174. Looking at that line it just says:
wp_deregister_script('jquery'); //deregister current jqueryWhat do I need to do from here? What seems to be the problem?
Forum: Hacks
In reply to: Custom Plugin Fatal errorsOk, so far today, I checked out the WP_DEBUG. I fixed most of the Notice errors. My theme must be old, cause it had a lot of errors for ‘get_settings’. I had to change all of those to ‘get_option’. I then had to add an extra line in each of the Theme php pages: `{
if(isset($value[‘id’])`) before the ‘get_option’.I also had to delete 3 of my plugins cause the were causing errors. Google Maps, Updraft – Backup/Restore, and WP Mobile Pack.
I’m now left with only a few errors. Two main ones that I can’t figure out:
Missing argument 3 for wp_register_sidebar_widget(), called in /usr/home/wash20/www/htdocs/wp-content/themes/connections-reloaded/functions.php on line 152 and defined in /usr/home/wash20/www/htdocs/wp-includes/widgets.php on line 604
and
PHP Notice: get_settings is deprecated since version 2.1! Use get_option() instead. in /usr/home/wash20/www/htdocs/wp-includes/functions.php on line 3467
For the PHP Notice, I went to the file that it mentions, and on line 3467 it only says:` trigger_error( sprintf( __(‘%1$s is <strong>deprecated</strong> since version %2$s! Use %3$s instead.’), $function, $version, $replacement ) );
The whole line of code that it is referring to is:` // Allow plugin to filter the output error trigger
if ( WP_DEBUG && apply_filters( ‘deprecated_function_trigger_error’, true ) ) {
if ( ! is_null($replacement) )
trigger_error( sprintf( __(‘%1$s is deprecated since version %2$s! Use %3$s instead.’), $function, $version, $replacement ) );
else
trigger_error( sprintf( __(‘%1$s is deprecated since version %2$s with no alternative available.’), $function, $version ) );
}
}`Forum: Hacks
In reply to: Custom Plugin Fatal errorsSo after I put the WP_Debug in the wp-config.php, what do I check out then? I looked at the script error logs again, and now there is only one:
PHP Fatal error: Call to undefined function add_action() in /usr/home/wash20/www/htdocs/wp-includes/wp-includes/update.php on line 337
I checked out the update.php and on line 337 is: add_action( ‘admin_init’, ‘_maybe_update_core’ );
Forum: Hacks
In reply to: Custom Plugin Fatal errorsSo, since I last posted about having this WP problem, my computer crashed cause of the S.M.A.R.T. HDD virus. I recovered from the virus, but delete my video drivers and couldn’t boot BIOS to fix the problem. Had to have it taken in to be repaired. I’m going to try to work with the WP_DEBUG option today. Hopefully I can find something there. I feel like it is the DB that is just not defined or something. I’ll let you know what I find in a little bit.
Forum: Hacks
In reply to: Custom Plugin Fatal errorsFor the past month and a half, I have been racking my brain going through coding. I never really knew anything about coding before May, but I think I might be a novice code writer before this is fixed.
Forum: Hacks
In reply to: Custom Plugin Fatal errorsI am running the newest version already. I thought that when I did an automatic upgrade, maybe things didn’t get copied right. At least, that is what I have been reading on other forums regarding similar problems.
The problem happened back in May. I got injected with malware. I completely wiped the site. Deleted everything from it and started over. Reinstalled wordpress and uploaded a backup from a week before the injection. Installed a f*ck ton of security measures after that.
It wasn’t working after the upload, so I tried changing themes. No help. Changed it back. WordPress had a few updates since…