billsaysthis

Having the same issue as tekitsune except that I get it when clicking publish on a post too. Though the post is published.

I just installed through the Add Plugin admin UI and get a different, and strange to me, error after clicking the Start Verification button:

Fatal error: Uncaught exception 'apiIOException' with message 'HTTP Error: (60) SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed' in /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/io/apiCurlIO.php:126 Stack trace: #0 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(191): apiCurlIO->makeRequest(Object(apiHttpRequest)) #1 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(171): apiOAuth->requestRequestToken('https://billsays...') #2 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/auth/apiOAuth.php(89): apiOAuth->obtainRequestToken('https://billsays...', '4db5d4c755eff') #3 /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification in /users/home/blazar/web/public/wp-content/plugins/official-google-site-verification-plugin/external/php-client/io/apiCurlIO.php on line 126

My server has curl installed:

curl -V
curl 7.19.7 (i386-sun-solaris2) libcurl/7.19.7 OpenSSL/0.9.8l zlib/1.2.3 libidn/1.15 libssh2/1.2.2
Protocols: tftp ftp telnet dict http file https ftps scp sftp
Features: IDN Largefile NTLM SSL libz

PHP -v: PHP 5.2.12 (cli) (built: Feb 15 2010 15:49:19)

Note that my site was verified a year ago, according to the Webmaster Tools link provided previously in this thread. Not sure if that matters.

I understand that, I’m a big fan of WordPress and this should be considered beta user feedback.

Pete, where is this fairly significant new feature documented?

The about page for 3.1–the only result if you search the Codex for “Admin Bar”–lists Admin Bar under Highlights, with no detail except a link to the trac ticket. I read that but while the comments probably make sense to the WP devs its too convoluted for me to follow and get much useful information from.

The philosophy is in general fine. But this is a significant UI addition, which are usually left to the user (that is, through the templating/theme system) and as such should not be unilaterally imposed. As I said, to default to on is fine as long as there’s a built-in way to turn it off for those of us who don’t want it.

I appreciate your assistance here.

Andrea, thanks for the prompt response.

Where is the define statement explained? I’m not installing a plugin to do this, that’s over the line.

Fair enough, though I’d think the delta in effort is small enough to not worry about putting it off and I don’t see how the option would impact the effort to perfect.

My bigger issue at the moment is that this just started appearing at the top of my blog pages and searching the Codex and here turned up no useful information. I’m sure it was listed in the changelogs and new features are to be expected running dev builds but at least some minimal entry ought to be made when people try to figure out what the heck this is.

Awesome, ipstenu, that was the answer!

Andrea_r: Yes, those ones are the ones I put in my .htaccess.

RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]

# uploaded files
RewriteRule ^files/(.+) wp-includes/ms-files.php?file=$1 [L]

RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule . index.php [L]

Did you update your .htaccess file for MuliSite?

I have one but didn’t change the .htaccess from the lines shown when I enabled MultiSite (that is, when I was shown the wp-config additions). What changes are necessary?

Amusingly, “remove /blog” never occurred to me as a search term since that wasn’t how I thought of the problem.

Okay, I figured out where to make that change. Created /newblog.

Now if I go to blog.example.com/newblog/wp-admin I get a 404 and the ‘Apologies, but the page you requested could not be found. Perhaps searching will help’ error page.

ipstenu: Thanks!

But! The main blog gets the /blog/ permalink stuffed in the url, so then you need to disable that.

This part is still unclear for me. Once created the path and siteurl for a blog cannot be altered, so I’m not certain how I would disable this.

Andrea_r: Any ETA for this fix? Is it in 3.1-alpha?

Failing that can you point to a forum post which gives explicit instructions for the workaround? I searched on a number of terms (upgrading 3.0.1 sub-directory fix, 3.0.1 sub-directory fix, upgrading 3.0.1 sub-directory install, etc…) and found nothing useful.

Thanks!

Check out https://www.kachingle.com (coi: I am the Tech Marketing Lead at Kachingle), which is a new way for readers to support your blog and others they read regularly.

We’re about ready to publish a WP plugin to simplify the process slightly but you can add us to WP now, as seen on our blog.

Given this is self-promotion I don’t want to go further here but am happy to respond via email (bill at companyname.com) if you have questions.

Weird, thought I tried that originally–works now but didn’t previously.

Thanks!