Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Hi – thanks for getting back to me. I think what’s going on is that the update for your plugin is showing as an update for another plugin I have. I’ll look into it further and start another topic if needed.
    Thanks!

    I am also having this problem on a staging site. Updating to the latest version make the columns go away on the front end of previous forms and makes the column break field option go away in the form editor.

    Hi,
    Just had a quick follow up for this. 1) is the reason this is happening because I’m working on a DEV (local) server, or is it because I am actually on a weird spam list somewhere? 2) Should I re-enable this when I take this live? Or is it like an appendix – you don’t need it.

    I’ve looked around a lot and haven’t been able to find a good, straight answer. Everyone says the same thing.

    Seems to me the only thing that is working these days is just to disable all the comment plugins (because FB changed something to break the functionality) and use the 2 blocks of code it would take to just manually enable FB comments.

    So I’m off to do that.

    Besides the broken moderation (which I think is pretty clearly a FB issue or change) this is a really easy and cool plugin.

    Thread Starter jiwicky

    (@jiwicky)

    After spending a ton of time trying to figure this out I realized that there were 2 things contributing to this. I’m not sure which one finally fixed it, but it is working better now.

    1) I had a function in my theme’s function file that was calling some custom thumbnail types and it was conflicting with another plug in. So you might want to do the plug in check thing – where you disable all the plug-ins scientifically until you find the one that is buggy. In this case I took out the code instead of deleting the plugin.

    2) I had spaces in my functions.php and media.php files. In other words, open those files up and make sure there are no extra lines in bottom. There shouldn’t be any empty space before the opening <?php or after the closing ?>

    Hope this helps. I almost went crazy trying to find what was causing this strange behavior.

    Thread Starter jiwicky

    (@jiwicky)

    I fixed this on my own.

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