Multiple Bugs / Issues

  • Resolved Oliver Campion

    (@domainsupport)


    2 years, 2 months ago

    Hello,

    Please find below all the reasons why we still use v2.6.0 of this plugin …

    • File manager folders are in a random order, not alphabetical
    • The directory names in the breadcrumb trail are uppercase which could be confusing as directory names are case sensitive
    • The breadcrumb trail starts with “HOME” and should start with “wp-content”
    • When clicking “Add files” to upload a file, you can choose a file but nothing happens. Only dropping files onto the browser window works.
    • When upload is complete, it says “Done” but the progress bar still animates which makes the user assume it’s still uploading.
    • When changes are detected in the text editor, the save button is hard to read as it has white text on a light background.
    • Several times we have found changes are not saved
    • Often the file interface gets stuck and folders won’t open
    • We get these PHP errors regularly on various different sites …?
      default.NOTICE: E_NOTICE: ob_flush(): failed to flush buffer. No buffer to flush {“code”:8,”message”:”ob_flush(): failed to flush buffer. No buffer to flush”,”file”:”/wp-content/plugins/wpide/App/Controllers/FileManager/DownloadController.php”,”line”:103} []
      EXCEPTION: Class ‘WPIDE\App\Utils\Exception’ not found in /wp-content/plugins/wpide/App/Helpers/PhpValidator.php on line 44
    • There’s a strange scrolling issue where items and sub-menu items (Users and Tools for example) further down the main Dashboard menu cannot be accessed because the browser bounces back to the top just as the mouse reaches the item.
    • We’ve mentioned it before but traversing spaces as tabs with the arrow keys and backspace key no longer works which is extremely tiresome when editing old code
    • Can we have an option to turn off auto closing of quotes and brackets?
    • When you return to the editor after (for example) a plugin has been deleted. Rather than go up to a folder that does exist, the file manager returns to the folder that no longer exists and just says “Empty Folder” which is not correct. Probably best not to remember where the user was because from experience you almost always aren’t going to that location anymore. Much better to always start from /wp-content/
    • debug.log won’t always open. Not sure what causes it but I think it might be a file size limitation. v2.6.0 alway opens the file no problem.
    • You still can’t scroll down because the editor is too close to the bottom of the page and requires some CSS like …? 
      ace_editor {
padding-bottom: 1em;
}

    Oliver

Viewing 15 replies - 1 through 15 (of 15 total)
  • Plugin Author XplodedThemes

    (@xplodedthemes)

    Hi Oliver,

    Thanks for the feedback!

    A new version (3.4.3) has been released with several fixes.

    Please take a look at the changelog:
    https://www.ads-software.com/plugins/wpide/#developers

    Please note:

    Can we have an option to turn off auto closing of quotes and brackets?

    This was previously resolved. You simply need to disable the behaviours option.
    https://d.pr/i/M8kopy

    You still can’t scroll down because the editor is too close to the bottom of the page and requires some CSS like …?

    This was also previously resolved by adding the css you provided.
    https://d.pr/i/s7Ki8s

    Let me know if we missed anything.

    Cheers

    Thread Starter Oliver Campion

    (@domainsupport)

    Awesome.

    I’ll check this all out and get back to you.

    Oliver

    Thread Starter Oliver Campion

    (@domainsupport)

    Hi,

    Getting there!

    • The option for traversing spaces as tabs seems to be working now which is brilliant but … when you go to options to change this, how do you go back to the editor? Am I missing a close button or do you need to refresh the plugin page?
    • That CSS didn’t work for scrolling down, sorry! My bad, please remove it again. I’ve had another look and changing the value of --wpide-tabs-height to ’49px’ seems to do the trick instead.

    <div data-v-7c79b10c="" class="wpide-preview bg2 d-flex" style="--wpide-tabs-height: 49px;">

    Oliver

    Plugin Author XplodedThemes

    (@xplodedthemes)

    Hi Oliver,

    Sorry for the delay!

    • The setting page, is actually a page, not a modal. To get back, simply use the following: https://d.pr/i/UBTHxA
    • The –wpide-tabs-height is dynamic and calculated automatically. From my end, setting this manually to 49px will make the editor height less than the actual window sometimes, leaving a white space at the bottom.
    Thread Starter Oliver Campion

    (@domainsupport)

    Thanks for that.

    The whole point is that a small gap / white space seems to be required at the bottom otherwise the click-drag-scroll doesn’t work.

    Do you want me to record a video to demonstrate with and without?

    Oliver

    Plugin Author XplodedThemes

    (@xplodedthemes)

    Yes please, it might help visualising the issue. Thank you

    Thread Starter Oliver Campion

    (@domainsupport)

    Entering fullscreen mode in Safari demonstrates the issue perfectly …

    https://www.dropbox.com/s/9818yspiem07v6m/WPIDE%20Scroll%20Issue.mov?dl=0

    Oliver

    Thread Starter Oliver Campion

    (@domainsupport)

    Can you let me know if you’ve seen this video yet? Thanks.

    Also, please can you explain why you block being able to edit /wp-content/themes/wpide/ and other files and directories? Seems a bit counter productive if a user wants to test changes to the plugin’s code? ??

    Oh, and whilst I remember, there’s often a need to edit wp-config.php, .htaccess or even WordPress core files (when debugging core issues) … perhaps an advanced option to be allowed access to edit all files? That would really be useful!

    Thanks,

    Oliver

    Thread Starter Oliver Campion

    (@domainsupport)

    – deleted

    Plugin Author XplodedThemes

    (@xplodedthemes)

    Hi Oliver,

    Yes, I have seen the video and clearly see the issue from your end, however, still not able to reproduce it from my end. Also, we did not get any other complaints concerning this issue, which is really weird.

    Can you please try this custom css code:

    
#wpbody-content .wpide-editor {
    --wpide-editor-scroll-height: calc(100vh - var(--wpide-header-height, 0px) - var(--wpide-adminbar-height, 0px) - var(--wpide-tabs-height, 0px) - var(--wpide-toolbar-height, 0px) - 5px)!important;
}

    Also, try playing with the last value, 5px. Try less or more and see which value fixes the issue. Increasing the value will reduce the editor height relative to the window height.

    https://d.pr/v/6rzaxM

    Let me know how this goes.

    The reason why we block access to the wpide directory, is actually the same reason why we can’t edit core files or the config.php. It’s because you can easily crash the site after saving a PHP file that contains errors, and our Custom Error Handler & Recovery Wizard wouldn’t be able to work correctly, which means the only way to recover is via FTP.

    There is also the fact that most WordPress host providers will have strict read only permissions on the wp-config.php file, so it won’t be possible for WPIDE to edit them.

    Thread Starter Oliver Campion

    (@domainsupport)

    Thanks … it looks like -1px is enough!

    #wpbody-content .wpide-editor {
    --wpide-editor-scroll-height: calc(100vh - var(--wpide-header-height, 0px) - var(--wpide-adminbar-height, 0px) - var(--wpide-tabs-height, 0px) - var(--wpide-toolbar-height, 0px) - 1px)!important;
}

    I can understand why you want to try to protect users from breaking their site but … by doing so you prevent all users from being able to edit what they want and if I were to break the site by doing so then I would indeed go in via FTP and fix the problem. So instead, when I want to quickly edit something in core when bug fixing an issue like this for example, I can’t use your plugin. I have to use FTP. Which renders your plugin completely useless in that situation. Perhaps an option to allow users full access to edit their entire site if they want to? Please?

    On another issue, I’ve discovered that your plugin doesn’t save files in some situations (but says that the file has been saved) and I’m still trying to find a precise way of replicating this problem so you can fix it. The last time this happened the php file had is_error() rather than is_wp_error() … I’ll report back when I have a definitive way to replicate the problem.

    Oliver

    Plugin Author XplodedThemes

    (@xplodedthemes)

    Thanks for this, I will apply it in the next update.

    Maybe we can add a safe mode option that is turned on by default and when disabled, all restrictions are lifted and a clear message would be displayed stating the risks. We will add this to our to-do list, however, I cannot guarantee a timeframe.

    Not sure for the saving files issue, is it happening in the latest version ?

    Thread Starter Oliver Campion

    (@domainsupport)

    That would be brilliant.

    And don’t worry about the saving files issue, I’ll update you properly when I know exactly what’s going on.

    Thanks for ongoing support.

    Oliver

    Thread Starter Oliver Campion

    (@domainsupport)

    Marking this as resolved … thank you.

    Oliver

    Plugin Author XplodedThemes

    (@xplodedthemes)

    Great, thank you for all your feedbacks!

Viewing 15 replies - 1 through 15 (of 15 total)
  • The topic ‘Multiple Bugs / Issues’ is closed to new replies.