Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Thread Starter nwipfli

    (@nwipfli)

    I’ve not changed the configuration and this suddenly stopped working. However, I’ve just upgraded to the latest version (3.1.1) of wp-members and now it is working again.

    Regards

    Thread Starter nwipfli

    (@nwipfli)

    No worry for the trouble, I could manage to downgrade until the fix was released. BTW, I’ve successfully tested 8.5.4 on my staging config and I have finally upgraded my production environment.

    Thanks for fixing this issue so rapidly.

    Thread Starter nwipfli

    (@nwipfli)

    I’ve setup a test environment on which I installed the plug in version 8.5.2, then I upgraded to 8.5.3 and the problem was reproducible. Then I tried downgrading to 8.5.2 and the problem disappeared. Therefore, I also downgraded my production environment (which kept all my existing addresses) and I will wait to see if there is a solution in this thread before upgrading again to 8.5.3.

    Regards
    Nicolas

    Thread Starter nwipfli

    (@nwipfli)

    Hi Chad,

    Sorry for my late response, I was away a few days. I’ve just upgraded to 3.0.6 and can confirm that the behavior I was encountering is now resolved.

    Thanks for your support
    Nicolas

    Thread Starter nwipfli

    (@nwipfli)

    Sorry but it seems that the culprit is really wp-members 3.0.5.1.
    I have daily backup with BlogVault, hence I’m able to say what plugin got upgraded on a specific date.
    On Sep 28 I had wp-members 3.0.4. On Sep 29 the backup contained the new version 3.0.5.1, hence I upgraded it on Sep 29 during the day and before my daily upgrade on Sep 29 at 11pm.
    I can also confirm that on Sep 29 the following plugins were upgraded:

    Akismet to 3.1.4
    Connections to 8.4.5
    WooCommerce to 2.4.7

    So, I’ve decided to use BlogVault in order to take my backup from Sep 28 (with wp-members 3.0.4) and use the migrate function to restore it into another location. After the restore, I confirmed that everything was working perfectly and when clicking on “Pages -> All pages” in WordPress, I was not redirected, but WordPress kept displaying correctly all the available pages. In other word, this issue was not reproduced with wp-members 3.0.4 and Firefox 41.0.1.

    Then I upgraded *only* wp-members from 3.0.4 to 3.0.5.1 and I tested again. At this time the problem appeared and each time I am clicking on “Pages -> All pages”, I am getting redirected to https://mywebsite/staging/wp-content/plugins/wp-members/css/admin.css?ver=3.0.5.1.
    Interestingly, if I use the browser Safari 9.0 or Chrome 45.0.2454.101 this issue does not happen even with wp-members 3.0.5.1. So, this auto redirect from “Pages -> All pages” happens only from wp-members 3.0.5.1 and with Firefox.

    Then I have un-installed wp-members 3.0.5.1 and re-installed 3.0.4. After re-installing back 3.0.4 this problem I have disappeared. Therefore it seems that this issue is really related to wp-members 3.0.5.1. The problem is that my downgrade from 3.0.5.1 to 3.0.4 confirmed that all the settings disappear, hence I do not want to use this workaround in my production website because I will lose all my settings, customization, etc… and I’m not ready to do that at this time.

    I can eventually use Safari or Chrome which seem to behave differently with this auto redirect triggered by wp-members 3.0.5.1, however I would really appreciate to get your opinion on what can happen here and why this issue starts with wp-members 3.0.5.1.

    Thanks

    Thread Starter nwipfli

    (@nwipfli)

    This issue started after Oct 5 because on Oct 5 I used the page editor to create a new one and it worked.
    I have a daily backup and I know what plugins got updated between Oct 5 and today. I deactivated all these plugins but the problem still happens.
    If I deactivate wp-member, the problem disappears. When I enable the Inspector in Firefox the problem disappears too (this is a weird behavior).

    This is strange because in the wp-member settings, the style sheet was set to “use custom url below” and the URL was just something like https://, and nothing else. I’ve never set this variable.

    If I delete the wp-member plugin and re-install it, do I need to re-configure everything (settings, etc…) for this plugin ?

    Thanks for your support

    Looks good on my side after the update to 3.0.0.2.

    @chad, thanks for your great support.

    As far as I’m concerned, I have upgraded to 3.0.0.1 about 45 min and my “Forgot?” and “Registration” links in the widget disappeared. Then after a while I realized that it was the options under the plugin settings which disappeared. The upgrade removed all my personal settings under the tab “WP-Members Options”. I had to check back the boxes I needed, specify the register link and the forgot password link.
    Beside that, all the registrations were approved automatically because the moderation checkbox was unchecked. I had to change this back.

    Hope the upgrade to 3.0.0.2 will not do the same.

    Thread Starter nwipfli

    (@nwipfli)

    The error has been fixed by the author of the other plugin “Photo Gallery”. Thanks.

    Yes, the issue is resolved on my side. Thanks for this speedy resolution.

    I’ve found my problem, it is related to the other plugin “WP Google Maps”. I’ve been able to recover from a backup (thanks BackupBuddy) and from this restore I’ve upgraded to the version 1.1.16 of Photo Gallery. Once I update an album, I’m getting a blank page but no error.
    Then I’ve upgraded “WP Google Maps” to 6.0.13 and I started to get the following errors:

    Warning: Cannot modify header information – headers already sent by (output started at /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-admin/menu-header.php:118) in /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-includes/pluggable.php on line 1121

    So, it seems that this issue is triggered by this other plugin “WP Google Maps”. I will contact its author.

    I’ve tried moving back to version 1.1.15 but I’m still getting the same error after updating an album:

    “Warning: Cannot modify header information – headers already sent by (output started at /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-admin/menu-header.php:118) in /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-includes/pluggable.php on line 1121”

    I’m not gettings this error with the galleries.

    I’ve also de-activated the other plugins I’ve updated but the error remains.
    I’m suspecting there is something wrong between the new version of WordPress 3.9.1 and Photo Gallery, but I could be wrong.

    Upgraded to the latest release of “Photo Gallery” today and I’m also getting the same error. See below what I’m getting when trying to update an album:

    “Warning: Cannot modify header information – headers already sent by (output started at /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-admin/menu-header.php:118) in /home/www/9ea6e214345c5766cb97be648b670d57/web/test/lafouleedebussigny/wp-includes/pluggable.php on line 1121”

    I’m looking for a solution.

    Thread Starter nwipfli

    (@nwipfli)

    I’ve upgraded to “WP User Avatar” 1.9.6 just released and now it is working successfully with BackupBuddy, there is no more conflict.

    Thread Starter nwipfli

    (@nwipfli)

    Hi, BackupBuddy is a plugin which allows you to backup/restore/migrate websites. This plugin has different menus and it was working fine until a few days when I upgraded your plugin “WP User Avatar” to 1.9.5.
    Before upgrading to 1.9.5, I was able to access all the menus in BackupBuddy, however after upgrading your plugin to 1.9.5, I was no longer able to access correctly the menus “Backup” and “Settings” for this other plugin “BackupBuddy”. Each time I was accessing these menus, the pages were not displayed correctly. Once I disabled “WP User Avater”, I was able to use BackupBuddy succcessfully. When I re-enabled your plugin, BackupBuddy was not working anymore.
    Therefore, it seems that “WP User Avatar” creates some conflict with this other plugin “BackupBuddy”. I have a screenshot which demonstrates the problem with “WP User Avatar”, please let me know how to can pass it to you.

Viewing 15 replies - 1 through 15 (of 15 total)