faina09

This is not my case; I didn’t installed a multisite, but TWO different WP code. Abs path for the first is e.g.:
/mydisk/wwwsites/mysite/
that contains
/mydisk/wwwsites/mysite/wp-content
/mydisk/wwwsites/mysite/wp-admin
/mydisk/wwwsites/mysite/wp-includes
the second is in
/mydisk/wwwsites/mysite/test/
and contains again:
/mydisk/wwwsites/mysite/test/wp-content
/mydisk/wwwsites/mysite/test/wp-admin
/mydisk/wwwsites/mysite/test/wp-includes

but probably this is not a good idea in WP… (I’m a newbie in WP)

I installed it on a subsite but it changed the root site code and not the sub!!!
I mean: the installation was in https://mysite.com/test that is still in WP3.3.2; I got WP3.4RC1 on the site https://mysite.com/
Even more: the upgrade changes files rights to 644, but my host needs 755; this was really a pain before I discover this (server 500 error)

I fixed – hopefully – all the issues, aligned to WP 3.3.2 standards, removed all deprecated calls and updated to jpicker last version 1.1.6.
I would like to give my work to the owner of this plugin and to all the people interested in it. Please contact me!

For me it’s important to have someone testing my code and suggesting enhancements. Glad to collaborate with you.

@divavocals My solution seems to work with no modifications in your theme’s functions.php file also if your blog is in a folder.
But I have a issue about password reset feature that seems not to work. Have you never tested it? As it is not possible to commit with no password, I would like to share the code with you, just write to me: [ email redacted ]

<br />
Error: Commit failed (details follow):<br />
Error:  forbidden by the server<br />
Error: Access to '/!svn/ver/452579/wp-login/trunk/themes/default/style.php' forbidden<br />

I will be very glad to contribute, but I’m a newbie in WP and in this forum and don’t know if it is correct – or even possible! – to commit to a repository. (don’t want to read all the stuff ;-)…)
I appreciate your work and workarounds but I didn’t still applied.
My fix is essential an upgrade to jpicker-1.1.6.min and a fix of some paths and variables.
I would like to work with you if you want.

I have the same issue, the theme is twentyeleven on WP3.3.2
and the error in /wp-includes/functions.php on line 3467
The error is generate by facebook-like-box plugin: https://www.dolcebita.com/wordpress/facebook-like-box/
(I searched the string ‘ register_sidebar_widget’). Ask the plugin author to fix.

the issue is still present!! WP 3.3.2, thema twentyeleven. Please fix!!

[28-May-2012 10:46:31 UTC] PHP Notice:  wp_enqueue_script was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>init</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in ../wp-includes/functions.php on line 3587
[28-May-2012 10:46:31 UTC] PHP Notice:  wp_enqueue_style was called <strong>incorrectly</strong>. Scripts and styles should not be registered or enqueued until the <code>wp_enqueue_scripts</code>, <code>admin_enqueue_scripts</code>, or <code>init</code> hooks. Please see <a href="https://codex.www.ads-software.com/Debugging_in_WordPress">Debugging in WordPress</a> for more information. (This message was added in version 3.3.) in ../wp-includes/functions.php on line 3587

Yes, seems to be a nice ‘first step’ for a great plugin. I found no alternatives. We could join together and go ahead developping… any one interested?