Forum Replies Created

Viewing 15 replies - 31 through 45 (of 136 total)
  • Ross Wintle

    (@magicroundabout)

    Duplicate issue: https://wordpress.org/support/topic/last-update-error-with-date-picker/

    Same problem here. Disabling ACF fixes, as does rolling back to v5.9.10.

    Ross Wintle

    (@magicroundabout)

    Rolling back to v5.9.10 fixes this for me. See the other thread:

    https://wordpress.org/support/topic/date-picker-conflict-with-advanced-custom-fields-plugin/

    Ross Wintle

    (@magicroundabout)

    Same problem here too. Disabling ACF re-enables the picker.

    There’s an error in the JS console:

    Uncaught TypeError: M.datepicker[(("_" + e) + "Datepicker")] is undefined - datepicker.min.js:9:35718

    Happy to help diagnose further if you want to get in touch.

    Thanks

    Ross Wintle

    (@magicroundabout)

    Just adding a vote for fixing this. I just updated a dev site to PHP7.2 and had this warning. It’s a simple fix!

    Thread Starter Ross Wintle

    (@magicroundabout)

    Hi there,

    Thanks for the reply. Yes, I’m running the latest version.

    I don’t want to turn off the whole meta box. I just want to turn off readability analysis and SEO analysis. It seems to me that if I do this I shouldn’t need to load the analysis JavaScript code.

    Thanks

    Ross

    Thread Starter Ross Wintle

    (@magicroundabout)

    Thanks, Tammie. You’re doing a great job here post-Gutenprompt!

    In the classic editor, pretty much everything you can do is on-screen. It’s easy to see what is possible. Excepting, of course, the screen options menu which is often unnoticed, and the “Kitchen Sink” (I know, it’s the toolbar now or something). Nothing appears or disappears. I know where I am and what I can do at any one moment. And that’s comforting.

    You know about affordances. The affordances just aren’t present. If you displayed ALL the controls at once it would be overwhelming. But displaying them on hover makes them hard to discover. And in many cases they aren’t clear: I’ve mentioned before the confusion of the cog and the three dots in the top right. Even after using Gutenberg several times over the course of several months I still don’t know what these really represent.

    The layout options for images are another example. The icons tell you what they do on hover with a tool tip, but at least three of them are unfamiliar icons for things that I probably don’t want to do most of the time. And then those blue re-sizing handles are sometimes present/sometimes not. I just find all the user interfaces icons, buttons, handles, menus, and so on so confusing.

    Occasionally the UI chrome all disappears and I need to wiggle my mouse to see where I am.

    There are also just too many blocks. If I’m writing I want paragraphs and headings and lists and that’s about it. That’s all the choice I need. Someone elsewhere mentioned that they write first and format later. This is probably what I do. Even things like images and videos are probably after thoughts for a simple blogger like me.

    Having individual blocks for headings and paragraphs just doesn’t make sense in this context. And the classic block is not promoted as an option at all in the same way that quotes, headings and HTML are.

    If you removed individual blocks for paragraphs, headings and lists, suddenly the UI would be much simpler because you could keep it all on screen at once without overwhelming people. This is basically what the Classic block does.

    At the moment I write in the WordPress editor. I can sketch an outline for a post. I can flesh it out. I can add formatting later. I can totally see myself, if forced to use Gutenberg, writing in something like Bear notes or SimpleNote or a classic block and then pasting in and/or converting to blocks later.

    But why should the simpler “just writing” experience be removed if that’s what people want?

    Ross Wintle

    (@magicroundabout)

    I’ve been hesitant to review, or comment on reviews of Gutenberg. But this thread very much sums up how I feel as a user.

    I find Gutenberg very difficult to “just write” with. I’ve explained my issues many times before:

    * UI popping in and out, sometimes hidden, sometimes not
    * multiple blocks for paragraphs
    * a proliferation of things I can do that I really don’t want to do when I’m writing…
    * …and UI for those things
    * Not being able to easily discover what I CAN do or how to tweak the user interface to make it simpler
    * Feeling like I have to use the mouse to do tasks that I used to do with the kayboard

    The phrase “it’s not intuitive” is coming up again and again in reviews. I think the core team HAVE to take this on board.

    Gutenberg, to me, is not functional enough to be a full page builder. And it’s way too complicated to be a content editor. Thus it is good at neither of these things.

    Thread Starter Ross Wintle

    (@magicroundabout)

    Thanks. Will look forward to this. Have continued conversation on the Vanilla Forums Forums…if that makes sense.

    Ross Wintle

    (@magicroundabout)

    A couple of other things to note:

    Gutenberg will not break sites

    You’re possibly/probably right in that Gutenberg will not stop sites from functioning. But they will significantly change the user interface. As one of many developers who creates WordPress-based sites for other people (my clients) I want my clients to be ready for this, and I want my code to be ready for it.

    I consider significant UI changes “breaking” as much as I consider code/functionality changes to be “breaking”.

    From my point of view, Gutenberg will significantly “break” sites.

    After the merge the default will probably be changed.

    Can we at the very least make this “a short time before the merge” so that my sites are ready to have Gutenberg deactivated BEFORE it arrives in the update?

    Thanks.

    Ross Wintle

    (@magicroundabout)

    I agree – I have about 150 sites that I manage for clients. I will want to update them to Gutenberg when the time is right. So my plan was to install this plugin using a tool like ManageWP on all the sites.

    But I just found out that installing the plugin is not enough.

    The default behaviour of the classic editor plugin should be to restore the classic editor. I don’t want to have to automate the changing of an option as well.

    Please make full classic-editor-restore the default function for this plugin.

    Plugin Author Ross Wintle

    (@magicroundabout)

    Hi there,

    To be honest, there’s not any updating to do. It works as advertised, I believe. I need to update the WordPress core version compatibility, but I think that’s all.

    And also, since making this, which fixed a problem for me, personally, I’ve discovered that CMB2 has this built in so I’d probably recommend using that instead.

    If you have any specific problems that you think need fixing, or feature requests for this plugin then let me know and I can maybe put some time into working on it.

    Thanks for your feedback

    Plugin Author Ross Wintle

    (@magicroundabout)

    Thanks for letting me know. And welcome to WordPress! 🙂

    I’ll set to resolved. But leave you with a note that this is far from the best plugin for doing what you’re probably trying to do. Feel free to look up others. I won’t be offended if you find something better.

    I’ll try to update the supported version and get it onto GitHub in the coming days.

    Plugin Author Ross Wintle

    (@magicroundabout)

    Hi there, and thanks for trying out the plugin.

    Just to rule out a simple thing, have you refreshed permalinks since installing it? Whenever new post types or taxonomies are created you need to do this to make the links work. To do this just go to “Settings -> Permalinks” and then click “Save changes” (you don’t actually need to save anything).

    I should probably document this for people, or include a call to the permalink refresh function in the plugin activation.

    Let me know if it still doesn’t work after that. I may need to update the code for creating the post types. I don’t know of any reason why it wouldn’t work on 4.6 or 4.7, but I’ve yet to test it and update the supported version number.

    I’ll try and update it soon. Let me know how you get on and if you have ideas for improving/enhancing the plugin then let me know. If you want me to publish it on GitHub so you can contribute code then also let me know.

    Thanks

    Ross

    Ross Wintle

    (@magicroundabout)

    Just want to thank you guys for fixing this so quickly. I’d probably have been able to do it myself but circumstances prevented me. Great work!

    Ross Wintle

    (@magicroundabout)

    Just wanted to report that I’m also having this issue on WordPress 4.7 with Gravity Forms 2.1.1 and WordPress Zero Spam 3.0.4.

Viewing 15 replies - 31 through 45 (of 136 total)