Not sure what that's related to specifically, but since it's one warning per row, my best guess would be something like the settings or move icon? Since this second error only appears to be occurring in conjunction with Supertable, it might not be yours to solve, but I figured that more information couldn't hurt. if one of your blocks contains a Supertable field (and that field is set to display "as a matrix"), it appears that you get one additional warning message for every row in the Super Table field per matrix block on your page. Maybe this is related to the "Add a Block" combobox / listbox button that appears below the matrix field if your screen width is too small to display all the available blocks as individual buttons.Īlso. Three matrix fields -> 3 console warnings Just having two (or more) matrix fields will cause the problem. It seems to occur regardless of whether or not any of the matrix fields have blocks added to them, and it also doesn't appear to matter whether or not any of the individual block types share a handle. I've found that I get this bug if I have two separate matrix fields on the same entry page. ddev/config.I also know this is an old bug report, but I think I've narrowed down a couple more causes for this bug. This will work in futureĬodespaces offer some default environment variables like CODESPACES=true, CODESPACE_NAME, etc. Normally you could use ddev launch as well, but there is a small fix needed since GitHub changed their forwarding domain in last week. Or use the preview (Simple Browser) in the editor: You can launch the website in a new browser window: Now it's time to run the vite dev server: I can still save Redactor fields withon a Craft 1.3 installation, but something must have changed down the road, because now all but one gets removed. The port type for vite should be HTTP (set by default). With older versions of Redactor / Craft it was possible to do this. We need to switch this manually each time. If we don't switch it to public, there will be CORS errors and javascript and styles can't be loaded via vite.ĭue to security reasons, GitHub codespaces does not allow to this to be set automatically right now. This change sometimes takes a minute or two to have effect. If you already have a live site, you could also pull in the database and assets (via ddev pull) instead of starting with a fresh install.Īfter the initial setup finished, we need to setup one more thing: Change the vite port visibility to "public": adds workaround for vite port exposing (since ddevs internal router is not used on codespaces).devcontainer/postCreateCommand.sh will handle all the setup steps automatically: Or you could use Matrix and keep using Redactor for the text parts of your article and have a separate block type for code. Instead you could use a Plain Text field for your article and get the formatting done with markdown. You can also use this dropdown menu on repositories: Dont use Redactor / a Rich Text field for code blocks is probably the only answer one can give right now. Clicking this button will run the CreateEntries service against the structure which has. There is a button in the README to launch it: use craftredactorField as Redactor // Get all fields fieldsService. It supports the development with vite, which was the tricky part. In the last weeks I experimented with GitHub Codespaces + DDEV.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |