alex1982

Thanks, that worked!

Hi Fotis, I tried a little to remove the font with your code and with some adjustments (replacing the wp_deregister_script call by wp_deregister_style), but it will always remove all styles from the parent theme. I guess that relates to line 108 in the parent theme’s function.php, whereas the font is set as a dependency for the olsen-light-style – key. If I remove any of the dependency, it will not add the olsen-light-style to the head.

wp_enqueue_style( 'olsen-light-style', get_template_directory_uri() . '/style.css', array(
		// 'olsen-light-google-font',
		'olsen-light-base',
		'olsen-light-common',
		'font-awesome',
		'olsen-light-magnific',
		'olsen-light-slick',
		'olsen-light-mmenu'
	), $theme->get( 'Version' ) );

Commenting out line 108 and line 99 (registering the font) works, but breaks update possibility.

Uhm, did you try to exclude a specific widget of your webpage with “noindex”? That’s not how the whole system works. The meta-tag “robots” is used for the whole page. To give this plugin a bad rating because you did not understand the basics of the meta tag usage is pretty unfair.

So I had the same error and I was wondering why, because I haven’t included any files manually, just installed the plugin into an almost fresh installation. I was using W3 Total Cache too, which was running before. I always emptied that cache after changing some wp-ratings options but the error still occurred. Nearby the mouseover and mouseout – functions did not work, mouseout caused broken images instead of the stars. I digged into the source code to find the bug and I found out, that the parseInt() – calls to all ratingsL10n – properties were not called, so ratingsL10n.custom was treated as string and the ratings_off– function tried to load custom images instead of the stars I choose.

tl;dr
Long story short – W3 Total Cache default options caused the problem finally. I had the JS minify option “embed type” set to “Default (blocking)” and this caused the error. Changing this option to “Non-blocking using JS” and clearing all caches made it work as it should :).
I hope this helps someone else, it took me some hours to find that out …

Just to mention it: Google decides whether its helpful for the user to show him the stars on serch result pages – if the structure test works, everything is alright and you have to wait or make your content more important.

Try setting the permissons to 777 to all those files. Got the same error and solved it by that.

Any line starting with “cp” means: Copy a file. In your case(s), where you shall use the shell commands, just use an FTP-client like filezilla and copy the requested files. In detail: navigate to
mywebsite/wp-content/plugins/w3-total-cache/wp-content/
and download the file
advanced-cache.php, then navigate to
mywebsite/wp-content/
and upload the file there. Then set the write permissions for this file to 777, if you don’t do so, the plugin tells you always to copy that file!

Do the same to other files, if requested.

If you get the message for the .htaccess-file, download that file (it’s under mywebsite/.htaccess, open it with a texteditor like notepad++, look for the lines:
# BEGIN W3TC Page Cache core
# END W3TC Page Cache core
Put the requested part
(in my case, Version 0.9.3 it was the following) in between these lines and save your file and upload it. MAKE SURE to backup your .htaccess – file first, if you do make any error. It avoids freaking out :).

# BEGIN W3TC Browser Cache
<IfModule mod_deflate.c>
    <IfModule mod_headers.c>
        Header append Vary User-Agent env=!dont-vary
    </IfModule>
        AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json
    <IfModule mod_mime.c>
        # DEFLATE by extension
        AddOutputFilter DEFLATE js css htm html xml
    </IfModule>
</IfModule>
# END W3TC Browser Cache

In my case there was some other code in between that lines, so I replaced them and it worked.

I recommend to NOT set the write permissions to 777 to the wp-config.php – file. If you did so, change them after your changes back to the original values.

Well, if I add the folder via FTP like set up onto the options page and set the rights to 777 the upload will work. I added two images for testing purpose with the category name “gallery_folder_added with 777”
Image 1: “Portrait-624×416.jpg”
Image 2: “Portrait-1024×682.jpg”

The following folder and file structure was created:

gallery_folder_added-with-777
gallery_folder_added-with-777/thumbs
gallery_folder_added-with-777/thumbs/thumbs_portrait-624×416.jpg
gallery_folder_added-with-777/portrait-624×416.jpg
gallery_folder_added-with-777/portrait-624×416.jpg_backup

So I am missing my second image, but the notification in the top right said: “2 files added successfully”

Klicking “Overview” shows me 2 images and 1 newly added gallery. If I click on the 2 images to view them the link https://mydomain.tld/wp-admin/admin.php?page=nggallery-add-gallery is called showing me, that I do not have the right to view this page (I am admin user).

Klicking on the list of galleries and selecting my new gallery shows me 2 images: “portrait-624×416.jpg” and “portrait-624×416.jpg” (so the same images!), both files link to the same source file.

I did the Plugin Check:
Check plugin/theme conflict
No conflict could be detected

Test image function
Could create image with 4048 x 3040 pixel

Check theme compatibility
Your theme should work fine with NextGEN Gallery

I hope this helps catching some other errors! Feel free to ask. I made everything on my testing space, so I can grant you access if you want to.

I can confirm, that the warning messages disappeared using 2.0.10 with wp 3.6 on all-inkl.com-hoster with 256M WP_MEMORY_LIMIT.

I am using the plugin Version 0.6.8 it with WordPress version 3.4.2 and it works fine. It also worked fine in WordPress version 3.4.1.

As far as I know, if you try to insert new users and pass them an ID, wordpress tries to update the user with the given ID.
See the Example in the reference: https://codex.www.ads-software.com/Function_Reference/wp_insert_user#Examples or see the source of the function: https://core.trac.www.ads-software.com/browser/tags/3.3.2/wp-includes/user.php#L1260 on line 1260, where it checks for the user-ID.
They use wp_insert_user with a given ID for updating … so the wording is a bit confusing.

In the code from EL45 at pastebin the ID ist set. Remove the ID from the code.

Right now I added lots of Users in WordPress 3.1.1 with the following code:

$user_data = array(
                'ID' => '',
                'user_pass' => wp_generate_password(),
                'user_login' => $loginName,
                'display_name' => $loginName,
                'first_name' => $firstName,
                'last_name' => $lastName,
                'role' => get_option('default_role') // Use default role or another role, e.g. 'editor'
            );
            $user_id = wp_insert_user( $user_data );
            wp_set_password($lastName, $user_id);

and I set up a default password to the user.
There is no need to set up an email address.
Required are at least user_pass and user_login but I didn’t tried this out.

Ah well! I just found that topic and thought, that this informations provided in here aren’t correct.
That topic should then marked as closed or resolved or something to do not irritate users like it irritated me ;).

Didn’t tried, if thats true, but I believe in Charles and so I set this topic to resolved.

Thats not correct. Try the extended doctype for RDFa:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML+RDFa 1.0//EN" "https://www.w3.org/MarkUp/DTD/xhtml-rdfa-1.dtd"> instead of your old doctype. That should validate.

Got the same error today while trying to activate it. Downloaded it via backend–>install.

WordPress Version 3.0.4