This came up while working on #3384
@Graham-72:
... I found that once I had made sure that my browser was using the revised plugin script (by forcing it to clear its cache and hard reload) I was no longer getting the
TypeError: Argument 1... error report.
@quicksketch:
... Yeah a problem with CKEditor is that it loads the JavaScript via it's own mechanism AND it's inside of an iframe, so plugin changes don't show up right away. Seems like something we might want to try and figure out if we can cache-bust based on Backdrop version numbers or something, to prevent this problem for end-users that update.
GitHub Issue #:
3460
Recent comments
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
custom module not showing up in modules list