• Resolved jaroslawistok

    (@jaroslawistok)


    Till yesterday all was working well but I guess because of autoupdate now nothing worked anymore. While the idea with extra menu for Plugin and numbered sidebars is good it doesn’t work for me. I looked for php Version as in thread before, it’s 5.6.30.

    I just cant’t place a widget in the side bar. After Update it desappears again.Was happy to have the older version as File and have installed it again…

Viewing 9 replies - 46 through 54 (of 54 total)
  • Updated from 1.04 to 1.1.0 – no problems.

    Thank you

    Plugin Author toddhalfpenny

    (@toddhalfpenny)

    That’s great news @upeuker, thanks for taking the time to let me know.
    I’ll try not to break anything in the future ??

    I updated to version 1.1.0 and got the following error afterwards although i purged the cache:

    Warning: Cannot modify header information – headers already sent by (output started at /www/htdocs/…./ra-plutte.de/wp-includes/general-template.php:2267) in /www/htdocs/…./ra-plutte.de/wp-config.php on line 110

    Warning: Cannot modify header information – headers already sent by (output started at /www/htdocs/…./ra-plutte.de/wp-includes/general-template.php:2267) in /www/htdocs/…./ra-plutte.de/wp-includes/pluggable.php on line 1195

    Edit: Apparently the error message displays only in case i am logged in. If you open any url on https://www.ra-plutte.de as a regular user it just shows the current date in the top left of the screen.

    Edit 2: The error message “Warning: Cannot modify header information – headers already sent by (output started at /www/htdocs/…./ra-plutte.de/wp-includes/general-template.php:2267) in /www/htdocs/…./ra-plutte.de/wp-includes/pluggable.php on line 1195” has disappeared after purging the cache again. The message regarding wp-config.php on line 110 and the date display in my frontend remains.

    Can you please have a quick look at this?

    • This reply was modified 7 years, 6 months ago by RA_NPL.
    • This reply was modified 7 years, 6 months ago by RA_NPL.
    Plugin Author toddhalfpenny

    (@toddhalfpenny)

    Hi @ra_npl,

    Firstly sorry to hear you’re seeing issues.

    I don’t believe this is the same issue as identified in this thread; would you please make a new support thread and include info about the theme you’re using?

    Thanks, Todd

    Hi toddhalfpenny,
    I installed the v1.1.0 now and it works as before! Great work, thanks for your support.

    Plugin Author toddhalfpenny

    (@toddhalfpenny)

    Super news @venus10, thanks so much for confirming the fix is working for you.

    Hi @toddhalfpenny,

    i am using Dorayaki Theme like other people here and so I waitet until today with updating your plugin, because I read there were errors.

    After updating today from 0.0.12 to 1.1.0 I still have the same problems: All widget-areas except one were removed and the widgets got deactivated.

    So I deleted the plugin-files and added 0.0.12 – now it seems to work again.
    Because I am not sure, if you can fix the problem with that theme, two questions:

    1. Was deleting the 1.1.0 files and uploading the 0.0.12 okay? Dont know, if there are problems with the database now…
    2. The functions of 0.0.12 are enough for me – could there be problems in the future, when I dont update your plugin?

    Thanks for your help!

    • This reply was modified 7 years, 5 months ago by alex879789.
    Plugin Author toddhalfpenny

    (@toddhalfpenny)

    Hi @alex879789,

    Sorry to hear that there is still a conflict with the Dorayaki theme. To answer your questions;

    1. Yes, this should be fine. There may perhaps be a couple of custom posts created, but these should not cause any conflict
    2. You could stick with 0.0.12, if the functionality is enough, though I will not be pushing any fixes or additional fixes into the 0.0.X releases. Features on the roadmap currently include auto adding sidebars to posts/pages before/after content/footers.

    Looking into specific theme conflicts is prob a stretch for me, especially a premium one, unless you were on paid support as part of the Pro version,

    @toddhalfpenny thanks for your fast answer and good to know!

Viewing 9 replies - 46 through 54 (of 54 total)
  • The topic ‘I definitely canceled autoupdates and am back to old version’ is closed to new replies.