It took me a while to figure out exactly what was going on but it’s actually a problem with WordPress. Bullseye installs version 1.0.49 of PureFTPd where in Buster v1.0.47 was installed. According to PureFTPd’s changelog here, globbing was removed from the NLST command in v1.0.48 (which makes sense since it’s actually not allowed according … Read more
From the looks of things, it’s a server issue. The WordPress theme uploader uses fopen() to transfer files from one location to the server. It looks like there’s a timeout or access error because a) fopen can’t find the file that it’s supposed to be transferring and b) the fread and fclose functions can’t find … Read more
A quick Google search confirmed your suspicion … this is likely an XML parsing error. Furthermore, some discussion on the forums suggests it’s caused by script insertion after a closing </rss> tag. If it is an inserted script, this is likely the result of a hack or an attack on your site or host. Another … Read more
WordPress can be inconsistent as to when is returns a WP_Error object and when it just returns false or string(0) when actually there was an error. I am not sure exactly what feedburner is returning that is not triggering a WP_Error from wp_remote_get() – but if you know wp_remote_get() will return an WP_Error, I would … Read more
I had the same problem before. When I asked my friend, who is maintaining the server, he answered me that it’s because of the server firewall. When he turned of the firewall, everything was ok (plugins can update, akismet can check for spam, etc.). So, if you’ve checked all your settings with Core Control (make … Read more
WordPress is pretty solid, usually misconfigurations get in the way. You want to make sure: you have your wp-config.php file properly set your database is accessible that your home and siteurl settings are properly set in wp_options table sometimes a plugin fouls things up, you can disable all plugins by unsetting active_plugins in the wp_options … Read more
This isn’t a WordPress problem. There’s no telling on a shared environment what the culprit might be. You probably don’t have access to your php.ini config, nor do we know how many websites your hosting company has jammed on your server. The very nature of a shared server is that each client shares the resources … Read more
You’re not closing the first if tag. /* Update user information. */ if ( !empty( $_POST[‘url’] ) ){ update_user_meta( $current_user->id, ‘user_url’, esc_url( $_POST[‘url’] ) ); } else{ delete_user_meta( $current_user->id, ‘user_url’); } Also, you should use esc_url_raw on a raw url and then if you’re echoing into the html use esc_url. You also shouldn’t save esc_attr … Read more
You could save the messages in a $_SESSION variable. This way, the values will be preserved untill you decide to remove them again. function save_message( $type, $message=”” ) { $_SESSION[‘messages’][$type] = $message; } function get_messages() { $return = ”; if ( isset( $_SESSION[‘messages’] ) && is_array( $_SESSION[‘messages’] ) ) { foreach( $_SESSION[‘messages’] as $type => … Read more
Since you cannot access the WordPress Dashboard with your user account you will need to use FTP or SSH to access the wp-content/plugins directory for your site and rename the plugin folder for wp-customer-reviews. Example: wp-content/plugins/wp-customer-reviews becomes wp-content/plugins/wp-customer-reviews-broken This will disable the plugin and allow you to log into the WP Dashboard again.