Jump to content

cb2004

Members
  • Posts

    542
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by cb2004

  1. @ryan great to see this module updated. Would you consider adding this feature to the next version: https://github.com/ryancramerdesign/ProcessExportProfile/issues/15
  2. I was thinking maybe it could be a bit simpler, for me all I need to do is check the modified date every 5 seconds and if it is different to what the page currently says then it just refreshes.
  3. Hi all. My JS/jQuery really struggles towards the end of the week, but I was just wondering if anybody has had the need to check the modified date of a page and if there is new to refresh. If not I will take a stab at it again next week. Have a good weekend all.
  4. @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.
  5. @Tintifax I recently had the same requirement: { "color_map": [ "595885", "Purple", "6a905e", "Green" ], "custom_colors": false }
  6. @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.
  7. @Pete TinyMCE version is available but i have discovered a few bugs:
  8. 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.
  9. @BitPoet loving the module so far, I have posted a few issues in GitHub.
  10. Can we have the option to change the dropdown label please? Sorry for totally spamming.
  11. 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
  12. 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.
  13. 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.
  14. 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.
  15. @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
  16. 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.
  17. 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.
  18. Within the field there will be a tab for 'Access'. You should be able to do what you need to do in there.
  19. So so good. Can't wait to put this on a photographers site tomorrow.
  20. I think this really depends on the agreement you have with your clients. If my clients are not on a monthly retainer, ProcessWire doesn't get upgraded until they want some work carried out on the site. If there were a slew of security issues with ProcessWire then an auto upgrade might be a good idea, but until any get found, I don't think its needed.
  21. You have done it again. I need a feature for a site and there you go and add it. Have a good weekend Sir.
  22. I just told my clients that they have started charging to use the api and luckily they are none the wiser. Still you can only retrieve a small amount of tweets on the free tier of the api.
  23. This module no longer works as it uses v1.1 of the API which is deprecated.
×
×
  • Create New...