vanilla74
Forum Replies Created
-
Forum: Plugins
In reply to: [wp-Monalisa] HTTPS issueYou’re right, I used better seach and replace plugin after switching to https.
I will test your new release now.Edit: it’s working! Thanks a lot!!
- This reply was modified 7 years, 11 months ago by vanilla74.
Forum: Plugins
In reply to: [wp-Monalisa] HTTPS issueIt was indeed a multisite installation. But I removed / disabled multisite long ago.
WP Version is 4.9.5. Theme is Mantra. Tested wp-monalisa with no other plugin active, same error.I managed to get it working by deleting the multisite check in your plugin.
Forum: Plugins
In reply to: [wp-Monalisa] HTTPS issueHi,
these are the errors I found in the debug.log:Notice: unserialize(): Error at offset 0 of 1 bytes in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wp-monalisa.php on line 144 Notice: unserialize(): Error at offset 0 of 1 bytes in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wp-monalisa.php on line 69 Warning: array_key_exists() expects parameter 2 to be array, boolean given in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wp-monalisa.php on line 71 Notice: unserialize(): Error at offset 0 of 1 bytes in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wpml_comment.php on line 35 Warning: array_key_exists() expects parameter 2 to be array, boolean given in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wpml_comment.php on line 37 Notice: unserialize(): Error at offset 0 of 1 bytes in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wpml_func.php on line 65 Notice: unserialize(): Error at offset 0 of 1 bytes in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wpml_edit.php on line 64 Fatal error: Call to undefined function get_blog_option() in /home/sites/site10/web/wp-content/plugins/wp-monalisa/wpml_edit.php on line 68Forum: Plugins
In reply to: [wp-Monalisa] HTTPS issueHi,
I have the same problem. After switching to https and activating monalisa I get a http error 500 for the admin-page, and on my front page all images have disappeared. I tried to delete the plugin, even deleted all hints of monalisa in the database, but no luck. As soon as I activate monalisa, everything’s broken.
Thanks for your help,
Vanilla- This reply was modified 7 years, 11 months ago by vanilla74.
Forum: Alpha/Beta/RC
In reply to: 2.7-b2-9665: FTP connection information doesn’t workOkay, I think the problem is with the hoster (funpic.de), because I tested the new beta3 with another hoster and everything is working as it should. On “Plugins – Add new” I see the popular tags for the first time, as this space was empty with the other installation.
The other hoster, funpic.de, is known to have problems with akismet as well. Something with external connections or so. Maybe this is connected.
Forum: Alpha/Beta/RC
In reply to: 2.7-b2-9665: FTP connection information doesn’t workI can only install plugins by manually uploading them with my ftp programm. When using the intergrated zip-uploader wordpress asks again for the ftp information and the same error occurs.
The automatic install feature doesn’t work either because when searching for a term or going to “featured”, “poplular” or “newest” I only get the message “an unknown error occured”.So I can neither install nor delete plugins from within wordpress. 🙁
Forum: Alpha/Beta/RC
In reply to: 2.7-b2-9665: FTP connection information doesn’t workError is still there using a fresh install (build 9705) with a clean database.
Forum: Alpha/Beta/RC
In reply to: 2.7-b2-9665: error with update-core.phpUpdate worked with 2.6, but never with 2.7. Tried with different builds, always the same error. WordPress also tells me (above the error line) that I have the latest version (using 9665).
Edit: I wiped out the existing wordpress installation including the database and did a fresh one. Now the error message disappeared. So one problem solved, but the ftp problem persists.
Forum: Alpha/Beta/RC
In reply to: 2.7-b2-9665: FTP connection information doesn’t workHost is funpic.de. WordPress Update doesn’t work, too (giving me a error warning in update.core.php).
It worked with v2.6.3, though.