hobbsy

I just updated a blog from 3.7.1 (with MP6 plugin v2.2.1 installed) to WP 3.8

Just a couple of notes on the behaviour:

The Core upgrade went smoothly.
On returning to view the plugins list afterwards, MP6 is still there but has now been disabled. WP tells me that there’s an update (v2.3 from v2.2.1) ready for MP6.

As it was just a test blog (that doesn’t matter if it breaks) I clicked on upgrade plugin. I’m not sure if my CHMOD permissions were wrong but I got this message (and then the plugin disappeared from my plugins list)

====
Update Plugin
Downloading update from https://downloads.www.ads-software.com/plugin/mp6.zip…
Unpacking the update…
Installing the latest version…
Removing the old version of the plugin…
Could not create directory. /public_html/wp-content/plugins/mp6/
Plugin update failed.
====

the /mp6/ folder still exists in the plugins folder but it is no longer listed within the WP dashboard plugins list (of course MP6 is now part of WP3.8 so I guess this was to be expected)

I will now just manually delete the /mp6/ folder via FTP

I also got this error when activating the plugin for the first time on my localhost – but it seems to work fine if I then visit my wp-admin URL.

After this, I can deactivate and re-activate fine without errors – just seems to be the initial activate that spits out the “The plugin does not have a valid header.”

Query Monitor v2.5.4
WP 3.7.1
Genesis 2.0.1
– downloaded zip from WP plugins page
– uploaded the zip via control panel

Thanks for creating this plugin – looks ace ??

thanks Jeremy ??

I also just noticed this too…

With Jetpack Comments enabled and running the URL through Google Pagespeed, under ‘Leverage browser caching’ I see:

https://s.skimresources.com/js/%5Brandomnumberhere%5D.skimlinks.js (expiration not specified)

(not sure if the [randomnumberhere] is unique to me so I’ve editted it above)

Why is this piece of Javascript being called?

If I temporarily disable the Comments part of Jetpack that .js line doesn’t occur

look in the settings page for the plugin and choose ‘bleeding edge nightlies’. That should let you update to the new 3.3

eg.
yourdomain.com/wp-admin/tools.php?page=wp_beta_tester

I’m having a similar problem regarding /attachment/ appearing in the URL

I believe it is because of the way your permalinks are set up

For example I am using:
/%category%/%postname%/

but if I switch to:
/%postname%/

the /attachment/ part magically disappears

Had the same problem:-
I deleted the WP Stats plugin and installed Jetpack. My stats now work.

@jasicom – download the Firebug extension for Firefox, and it should enable you to narrow down the CSS rules driving their floating widget

https://getfirebug.com/
https://addons.mozilla.org/en-US/firefox/addon/1843

I was also getting the error message:

Fatal error: Call to undefined method WordPress_Module::_weak_escape() in /home/username/public_html/wp-includes/wp-db.php on line 515

For me the plugin causing this error to display was Redirection

I renamed the folder for that plugin:

plugins/redirection

to

plugins/redirection1

and it let me log-in to my admin area…

JLCarbwood – could you maybe add that value as a custom field to the page/post?

and then pull it into the code you posted above:

<?php echo do_shortcode(‘[nggallery id=<?php echo get_post_meta($post->ID, “nameofyourcustomfield”, true); ?>]’); ?>

I’m not a NextGEN or WordPress expert so it’s just a guess. Worth a try?

I think what dpaule and dimospbru are referring to is the fact that currently NextGEN uses URLs with a structure like:

example.com/my-folder/?pid=375
example.com/my-folder/?pid=376
example.com/my-folder/?pid=377
etc…

but the question mark isn’t SEO-friendly (as I believe Google will treat 375 to 377 as one page?)

a better solution would be:
example.com/my-folder/375
example.com/my-folder/376
example.com/my-folder/377

How can we achieve this within NextGEN — a bit of .htaccess magic, or is this option built in to NextGEN?

The pretty URLs SEO situation is the thing I’d most like to see improved in NextGEN. It’s frustrating that I can’t figure out how to make them look nicer by myself, as other than this I love the plugin. Please could you consider implementing this upgrade Alex?

I have the same problem as fluvius…

I tested on a fresh install of WordPress 2.7 on my local WAMP PC.. with Discography the only plugin installed.

I am using Firefox 3.0.5 (but I also tested in IE6) – same error both times…

Warning: array_pop() [function.array-pop]: The argument should be an array in C:\wamp\www\_testing\wordpress3\wp-content\plugins\discography\discography.php on line 628