I searched for all Console.log() references and there are a ~4 active in public.js which are filling up the developer console.
But worse still is admin.js which has a 12+ console.log messages being dumped to the developer console log.
This is debugging code not something that should be active on public releases of your plugin.
Hello, sorry, we will check and fix this. Thank you for the feedback!
Hi,
This was not fully addressed in your recent 3.0.63 update.
Public.JS still has about 4 console.log message entries.
- console.log(“adding items CSS”)
- console.log(“viewportitem update”)
- console.log(t)
- console.log(“slick-destroyed”)
Admin.js is fixed though.
I’m confused your newest release has reinstated the javascript console debugging code in admin.js which you had fixed in 3.0.63.
3.0.64 also doesn’t fix the code in public.js I previously reported.
We have gone backwards in fixes ;-(
Someone needs more sleep; your developer has released 3.0.65 to fix the issues reported BUT the files:
- admin.js
- public.js
are untouched and unchanged. So this release is a “no-change” package.
3.0.65 still contains the same debug code as in previous releases.
Hello, will send this to developers, sorry for the inconvenience.
You need to hire a new developer. Their attention to detail is missing.
3.0.68 update fixes the console.log messages in public.js.
BUT again misses the 20+ messages in admin.js.
I can see I am wasting my time reporting this.
