michaelkallweitt

Are you kidding me? My website exists for some time already, and the “courtesy” of installing your piece of … software … wouldn’t have gone unnoticed over the last months.

There already were a number of complaints about this issue in the reviews for your plugin, therefore it is safe to assume that your copy-and-paste answer to all of these comments is wrong.

Giving a plugin access to my site is, at least partly, an issue of trust. Like others I decided that you no longer deserve to be trusted, therefore I switched to Yoast SEO having used AIOSEO for many years.

It might help to visit the file system of your WP installation, and remove the wp-super-cache directory from /wp-contents/plugins/

In my case (I could still log in), I manually installed the plugin from the dashboard, then disabled caching in the settings.

OK, after I manually installed WP Super Cache, the errors are still there.

My site URL is https://www.wasfuereintheater.com/

Can someone help me to fix it?

Must have been a plugin problem. I deleted all the plugins, then reinstalled and activated only those that are absolutely essential for running my site. Now everything’s fine again.

It only happens with this specific function. Update to 2.5.10 didn’t bring any changes.

May I add that my server uses PHP Version 7.0.6, which is marked as STABLE by the hosting company.

Nein, die Counter sehe ich nicht, auch nicht wenn ich das entsprechende Feld aktiviere.

Aber das wird ja schon bei den Einstellungen angezeigt: “PHP version 5.4 or better is needed to enable the backend.”

2.1.2 funktioniert!

phpinfo() sagt:

System Linux m07s4-2-15db.ispgateway.de 2.6.32.53-grsec-x86_64 #4 SMP Wed Jun 11 14:57:07 CEST 2014 x86_64
Build Date Dec 9 2014 11:27:07
Configure Command ‘./configure’ ‘–with-mysql=/usr/local/mysql’ ‘–with-config-file-path=/usr/local/php5’ ‘–with-mysqli’ ‘–with-openssl’ ‘–with-gd’ ‘–disable-force-cgi-redirect’ ‘–enable-discard-path’ ‘–enable-ftp’ ‘–enable-calendar’ ‘–with-libxml-dir’ ‘–with-jpeg-dir=../jpeg-6b/’ ‘–with-ttf’ ‘–with-freetype-dir=/usr/include’ ‘–with-gettext’ ‘–with-zlib-dir=../zlib-1.1.3/’ ‘–with-png-dir=../libpng-1.0.6/’ ‘–with-gdbm’ ‘–with-ndbm’ ‘–enable-dba’ ‘–enable-wddx’ ‘–enable-bcmath’ ‘–enable-exif’ ‘–with-curl’ ‘–enable-dbase’ ‘–enable-inline-optimization’ ‘–with-gnu-ld’ ‘–with-zlib’ ‘–with-mcrypt=’ ‘–with-xsl’ ‘–enable-wddx’ ‘–with-mhash’ ‘–with-pgsql’ ‘–with-bz2’ ‘–with-pdo-mysql=/usr’ ‘–with-iconv’ ‘–enable-soap’ ‘–with-imap=/usr/local/imap-2007e’ ‘–with-imap-ssl=/usr/local/imap-2007e’ ‘–enable-mbstring’
…

Jetzt tritt der Fehler in Zeile 597 auf.

Ja, mit 2.1.1 funktioniert es!

Edit: Sorry, ich habe es mit dem anderen Shariff-Plugin verwechselt. 2.1.1 wirft immer noch einen Fehler aus!

PHP-Version ist laut Dashboard 5.2.17.

Wie ich an die weiteren Informationen komme, wei? ich nicht. Mein Hoster ist pagejumper.de

German capitalization rules are somewhat tricky, therefore it would be best not to touch anything, but rather leave the image descriptions just as they are entered into the respective fields.

Sorry to bother you with this, but as much as I like the plugin, correct spelling and grammar are somewhat essential to my professional representation.

Nevertheless I wish you Happy Holidays, and thank you for your work!

Michael.

I upgraded the plugin to version 1.5, but I don’t find a setting for the capitalization.

You can see my gallery at https://www.wasfuereintheater.com/galerie/

If you hover the mouse over one of the images, the title is still capitalized. Same thing happens when you click on single images.

I can’t even get the authentication to work!

When I press the “Authenticate with your Google account” button, I get forwarded to the Google Accounts site, with a banner “We are unable to verify the name associated with this application because it runs on your computer, as opposed to on a website. We recommend you do not allow access unless you trust the application.”

If I try ignore the warning, my site still won’t have the authentication. ??

I thought that I had found a bugfix earlier today, but it didn’t work. :/

The error seems to be in line 57 of frontend/class-frontend.php:

if ( in_array( $current_user->roles[0], $this->options['ignore_users'] ) ) {

As the bug doesn’t seem to affect site visitors, I’m waiting for an “official” solution.