Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


cb2004 last won the day on October 1 2023

cb2004 had the most liked content!

About cb2004

  • Birthday 04/20/1982

Profile Information

  • Gender
  • Location

Recent Profile Visitors

5,015 profile views

cb2004's Achievements

Hero Member

Hero Member (6/6)




Community Answers

  1. @Stefanowitsch in the 'Input' tab of the field settings, there is a 'Custom settings JSON' area. You can put it in the 'JSON text' field, or if you need to reuse it, create a file on your server add the above to the file and point to it using the 'JSON file' option.
  2. @Tintifax I recently had the same requirement: { "color_map": [ "595885", "Purple", "6a905e", "Green" ], "custom_colors": false }
  3. @ryan summed it up really nicely. I mentioned earlier about Swiper, and Splide etc, completly forgetting they have moved to ES6 some time ago. Front end modules would be advantageous to remove jQuery I agree (if we are thinking very long term) but why remove it in the backend. I also hate vanilla JS, always have always will (not as much as I hated Flash), so I will continue to champion jQuery. It has such little overhead (especially the slim build) that it makes it strange to me that Lighthouse complains about Google Fonts, YouTube embeds, Analytics and lots of other things but not jQuery. They are already talking about what will be in jQuery 5 so it's here to stay I think.
  4. @Pete TinyMCE version is available but i have discovered a few bugs:
  5. Nice work as always. I upgraded 2 sites in development this week to jQuery 4 and everything worked just fine. Scripts we had made, Swiper, Splide, Fancybox and a few other go to scripts all worked fine. I think it's about 10% lighter as well, maybe more which is always welcome. Nice to see one of my request hit the commits. Have a great weekend.
  6. @BitPoet loving the module so far, I have posted a few issues in GitHub.
  7. Can we have the option to change the dropdown label please? Sorry for totally spamming.
  8. The double click dialog is not working for me. Also I am getting a console error looking for a CSS file /site/modules/HannaCodeDialogTiny/HannaCodeDialogTiny.css?v=0.1.2
  9. Just as an aside, it might be worth mentioning you have to enabled those checkboxes for the module to work. I am going to begin testing now.
  10. OK I looked at that line and it is to do with the default open tag, the next line is to do with the close tag. I went into the module settings for TextformatterHannaCode and clicked 'Submit' without making any changes and now everything works.
  11. There seems to be an error for me on the latest ProcessWire: Fatal Error: Uncaught Error: Class "TextformatterHannaCode" not found in site/modules/HannaCodeDialogTiny/HannaCodeDialogTiny.module:84 There was an upgrade to TinyMCE in this version so I am not sure if that has anything to do with it. I have selected 'hannadialog' and 'hannadropdown' in the 'External plugins to enable' section of the field.
  12. @ryan looks like this was added in 4.22.0 and can be disabled: https://ckeditor.com/docs/ckeditor4/latest/api/CKEDITOR_config.html#cfg-versionCheck
  13. Could we see a version 3.1 in the dev branch this week? I am always wondering what it would take to get that digit rising.
  14. I have never used the access for fields before. I am sure you could do this with a hook, but sounds like it should be part of the core as well.
  • Create New...