Viewing 14 replies - 31 through 44 (of 44 total)
  • Plugin Author Greg Priday

    (@gpriday)

    Would anyone be able to check out the latest development version of Page Builder? This should fix the issue. There are a few other things that I need to check for this release, but once we’ve had confirmation that this fixes the issue, I’ll be able to tick this off the list.

    You can download the development version from out Github page:

    https://github.com/siteorigin/siteorigin-panels/

    I got blank admin page with development version… Even WP debug says nothing, so blank.

    Plugin Author Greg Priday

    (@gpriday)

    Thanks for taking a look digitohter. I really appreciate it.

    Something I forgot to mention is that you’d need to disable the version of Page Builder that you have installed before installing the development version. Having both versions active at the same time will cause problems.

    For now, if you login to your site’s FTP and navigate to wp-content/plugins/ and rename the siteorigin-panels folder to _siteorigin-panels, WordPress will disable it.

    Greg, thank You, but I know how to install development versions ??

    I have deleted whole siteorigin-panels folder via FTP, renamed siteorigin-panels-develop to siteorigin-panels and uploaded via FTP.

    With my test WP site I got error with development version when I try to activate the plugin: Fatal error: Can’t use function return value in write context in …/wp-content/plugins/siteorigin-panels/siteorigin-panels.php on line 280
    (path start removed)

    Plugin Author Greg Priday

    (@gpriday)

    Oh oops, I hadn’t pushed some changes to the Github repo. Can you try downloading a fresh copy and check again.

    https://github.com/siteorigin/siteorigin-panels/archive/develop.zip

    Thank you, Greg! With development version now all seems to be working fine again.

    Plugin Author Greg Priday

    (@gpriday)

    Fantastic. Thanks for checking. I’ll be doing a hotfix release shortly.

    Thread Starter Optimizr

    (@william-greatman)

    Sorry for my late reply!

    @misplon
    Disable the visual editor when writing is not checked!

    @greg
    I too fine with development version.

    Thank you very much for taking time to review this issue and sorry for being me who raise this issue.

    Plugin Author Greg Priday

    (@gpriday)

    Thanks for bringing it to our attention myowin. The feedback is a huge help.

    I’ve just released version 2.1.5. The update includes this fix. WordPress should be prompting you to update shortly – after some caches refresh.

    https://downloads.www.ads-software.com/plugin/siteorigin-panels.2.1.5.zip

    Thread Starter Optimizr

    (@william-greatman)

    Thank you! I really appreciate your support and effort.

    Thread Starter Optimizr

    (@william-greatman)

    I think “post loop” is not working after update. It can be error from somewhere outside of your plugin. But in case if it’s from SO pagebuilder, just want to inform you before other issues raise. I’m about to solve my problem in another way. ??

    Plugin Support Andrew Misplon

    (@misplon)

    @myowin, please can you explain a bit further as to what the problem is with the Post Loop widget. Thanks.

    Thread Starter Optimizr

    (@william-greatman)

    Sure! Before update, it was fine. I put the “post loop” widget in SO widget area. I set number of post to 4 in Setting>Reading because I only want 4 post on home page. All 4 posts appear.

    But after update to final release of SOpb, it shows “it queried 4 posts” in edit page screen but only 1 post is appear on home page which also is incomplete. Now, I’m using original wordpress’s “latest posts” on home page and it is fine.

    Plugin Support Andrew Misplon

    (@misplon)

    Can you try editing the Post Loop widget and then click the Build posts query button. From there, try manually setting the Posts per page in the field provided.

Viewing 14 replies - 31 through 44 (of 44 total)
  • The topic ‘Cannot update options (forms) of other widges’ is closed to new replies.