Bill Huber
Forum Replies Created
-
I finally resolved this problem by deactivating WP-Statistics, activating Plainview Activity Monitor, and then activating WP-Statistics. Both Plainview and WP-Statistics use composer.
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Problems with PublicizeI updated Jetpack version 2.9.2 and that fixed the problem for me.
Sorry, I did not get back to you earlier. I have been a little busy with my day job. I was curious about what were the developers trying to fix since the code change seems unrelated to Live Writer and fixing the problems with Admin/Editor Only. I just know that the old code works and the new code does not work. Here are two blogs I am using the 2.8 version of publicize.php on successfully. Everything else in Jetpack is 2.9.
Sorry to jump in here but I am guessing by trying to fix the problem with “Publicize for Admin and Editor only” you created a new problem with publicizing posts created using Live Writer and maybe other methods. I went back to the 2.8 version of publicize and it works for me. I will do more testing today on another blog I have to confirm that 2.8 still works. Here is the code I am talking about.
304,308d303 < if ( false == apply_filters( 'wpas_submit_post?', $submit_post, $post_id, $service_name, $connection_data ) ) { < delete_post_meta( $post_id, $this->PENDING ); < continue; < } < 312a308,312 > > if ( false == apply_filters( 'wpas_submit_post?', $submit_post, $post_id, $service_name, $connection_data ) ) { > update_post_meta( $post_id, $this->POST_SKIP . $unique_id, 1 ); > continue; > }
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Problems with PublicizeSince I was curious I installed the 2.8 version of publicize.php. Then I wrote a test post using Live Writer and published it. It posted on my web site and published to Twitter just fine.
Thanks, I followed your instructions and it worked like a charm. I found that I had to delete the account on my WordPress for Android client and re-install it to get it by the “statistics could not refreshed at this time” error message. That allowed me to update the userid it uses to access WordPress.com.
Forum: Fixing WordPress
In reply to: WP installation keeps reverting to default themeToday I found a solution to my version of this problem and it maybe helpful to you. Over the last week I had made several changes to a website including adding a new theme, Mistylook. Sadish, I think you are familiar with it. After a long day of trying to debug this problem I decided to give up and change the logic in the validate_theme function so that it always said it found the theme. Surprise, surprise, it still reverted to the default theme. The only way this could happen would be if a different admin_functions.php was being used. One my website changes was creating an addin domain and moving the website to a new directory. My problem was that I had internet bots scanning my old web site directory. Every time they went to the old directory, the “old” WordPress admin_functions.php changed the theme back to the default theme because it could not find the two theme files, index.php and style.css. When WordPress cranks up it sets the ABSPATH variable to the directory it is started in. Subsequently it will make all file references relative to this directory. My theme did not exist in this directory structure so it set it back to default. Enjoy!