Nico
Forum Replies Created
-
You did not read the sticky post. Thanks anyway for reporting this even if here is the wrong place. I found a bug that caused outdated add-ons to be executed.
This would not happen if you also updated pro to latest 7.1.4 but good that this helped catch a bug. If you now update ARVE only and not Pro it will simply not execute any code from the pro-addon (no errors) but you need the latest for it to work again.
Forum: Plugins
In reply to: [Draft - Tailwind CSS for WordPress.] Source code missingAnswer from the plugins team (Of course I was right):
Short answer: yes – The Plugin Directory requires code to be (mostly) human readable. If you ship compiled/minified JavaScript you must also make the human‑readable source available (either include it in the plugin package or provide a clear link in the readme to a public repository and build instructions).
Clarification on minification vs mangling/obfuscation:
- Minification (removing whitespace, comments, shortening non-symbol names where readable) is acceptable for delivery, but it must not prevent humans from reasonably understanding or auditing the code.
- Uglify’s mangle option renames identifiers (variables/functions) to very short names (a, b, c, …). Combined with other transformations this often amounts to obfuscation — making the code effectively unreadable. That kind of mangling/obfuscation is disallowed under guideline #4.
Thanks,
WordPress Plugins Team—–
Yesterday you answered, marked it as resolved within minutes, took like three attempts to give me the code over a time of like 3 hours or something like that.
You could dump the code on Github/Gitlab/Codeberg/whatever. You could have quickly zipped up the plugins and send it. I still not have what I asked for. I also think it’s a security concern to have 200k unreadable code that takes ages to decipher without the source to it.
Now comply with the guidelines! Here I thought I can learn from your code, I could possibly be done with it. If I invested the time trying to figure this out on my own or with the help of AI. But this is about principle now.
Forum: Plugins
In reply to: [Draft - Tailwind CSS for WordPress.] Source code missingI indeed consider what you are going resisting. I asked for the class selector the first time. I totally fail to get why this takes endless attempts to give me what I asked for. What about “class selector” was so hard to understand?
Also, you cherry-picked some text about optional tool chain description from the guidelines and ignored the rest. Ignoring the fact about human-readable … I wrote an email to the plugin team asking for clarification on the guidelines. The way I understand it, you must put the uncompressed readable actual sources into the plugin or link to the sources somewhere else!
Leaving aside what is required or not, you seem to be willing to share but in the most annoying way possible, with little snippets that I need to copy and paste now and try to build together that reference files I do not have …import ClassPicker from '../../components/class-picker';This is a component you wrote? You still have failed to share the damn code to actually build it, this is crazy. It seems similar to the WordPress tag selector, but you need comma or enter to separate tags and this operates by spaces, it pulls in a list of classes for quick selection list. I still do not have the code for it, just weird what you are doing. Like, what is keeping you from putting the source out?
And you do not need to tell me about your one-man operation, I am a one-man operation myself, I maintain my own plugin here for 13 years! And I have the sources in my plugin and on Github. It’s not hard. If you can copy and paste them here you can dump them somewhere, I really do not get you.
Instead of putting the sources out in some way, you prematurely marked this as “solved” and dumped some meaningless BS with “there is hardly anything in there”. Yeah, only 16k lines prettified unreadable code, considering that wp-scripts that you seem to be using does actually not compile WP internal deps into the file that is quite a lot … but you were eager to jump on the fact that you do not have to share you build process … seems to be wp-scripts, you act just weird.- This reply was modified 6 months, 3 weeks ago by Nico.
Forum: Plugins
In reply to: [Draft - Tailwind CSS for WordPress.] Source code missing“obfuscate feature, uglify’s mangle” compiling is THAT it’s making it unreadable for humans! THAT IS “Making code non-human readable” or “obfuscate”
Why are you resisting putting the source into the plugin as required? I also again fail to see how your other copy&paste shows the code that builds the class selector. You again post code I did not ask for.
Just put the source into the plugin that you use to build the plugin, as required.- This reply was modified 6 months, 3 weeks ago by Nico.
Forum: Plugins
In reply to: [Draft - Tailwind CSS for WordPress.] Source code missing4. Code must be (mostly) human readable.
Obscuring code by hiding it with techniques or systems similar to
p,a,c,k,e,r‘s obfuscate feature, uglify’s mangle, or unclear naming conventions such as$z12sdf813d, is not permitted in the directory. Making code non-human readable forces future developers to face an unnecessary hurdle, as well as being a common vector for hidden, malicious code.We require developers to provide public, maintained access to their source code and any build tools in one of the following ways:
- Include the source code in the deployed plugin
- A link in the readme to the development location
We strongly recommend you document how any development tools are to be used.
—-
The above is from the plugin guidelines, AFAIK they have not changed, for block only plugins there are additional guidelines come on top of the general plugin guidelines.
Forum: Plugins
In reply to: [Draft - Tailwind CSS for WordPress.] Source code missingCan you point out where this is written that the source is not required anymore?
I am interested in how you build the entire Gutenberg sidebar, specifically the class selector, what you just pasted is not really helping.Thank you, yes, I am grumpy at times. This one man operation doing support and all the things can get frustrating.
Card mode for Pro is coming soon.
Forum: Plugins
In reply to: [Redis Object Cache] WP CLI help does not actually show a command to flushI just found out that WP CLI has its own
cachecommand to work with the object cache plugin independent, so this should probably be mentioned here.Nevermind, I think I modified the plugins files by accident (with phpcs fixer) or something. I just reinstalled the plugin and it’s working.
I missed that the stable update was out. I can not confirm it not working. I checked with AIOSEO 4.7.7 and 4.7.7.2 and they both work with the latest ARVE version. I will remove the notice from ARVE in the next version as this seems to be fixed.
Are some of your sites hosted on WP Engine? I have a report that the button supposedly does not work on WPE but its just one report and I have no confirmed this or know if its maybe because of a incompatibly with another plugin. If this is the case please contact WPE for a fix. I do not host with them so I can not test it myself.
They might be messing with importmap or JS modules the way this plugin did. The JavaScript modules and WP Interactivity APIs are quite recent and there might be other plugins / theme code that are doing it the wrong way.
And btw: Awesomemotive, the owner of this and many other plugins is a shady company who ADMIT they mark topics as “resolved” as soon as they respond here. They do it so they can FAKE the number of “resolved topics” on their plugins pages. Please leave a negative review for this shady practice. You can also change it to “not resolved” as a thread starter and watch them just rudely mark it as resolved again! This one seems to be actually resolved now from what I can tell.
I just want to apologize and correct myself I accused the “Supportcandy folks” of something above and if mod can change that to “All In One SEO folks” I can no longer edit this. I got that mixed up. AIOSEO is the same company Awesomemotive so it makes a lot of sense.
As for the issue, I think I did find out what the cause is, and its bad EDD code but you rather seem interested into continuing wrongfully marking this as resolved so …
Well, you would need some basic JS or the WP HTML API to add the data attribute. It’s out of scope to teach you how to code. I will just add the data attribute to the next version.
No offense, but I find it funny that you need to ask them to explain what this thing does that you say you need. I do not see any fancy animations or anything besides some basic smooth scroll on the site you linked.
You failed to explain what exactly the actual issue is. I asked you how an element is supposed to “responding” and you did not explain it. It seems that while hovering over videos with the mouse cursor and scroll with mouse wheel, the scrolling seems not work correctly and gets stuck or acts weird. It that what you mean? I guess this is it, why did you not explain this? Why do I need to find this out myself?
And this proves my point, from what I learned from an article, scrolljacking is bad. This is what Brave Search AI tells me for “scroll hijacking is bad”.
Scroll Hijacking Consequences
Scroll hijacking, also known as scrolljacking, is a design pattern that alters the normal pace or direction of scrolling on a website. While it may seem innovative or attention-grabbing, it can significantly harm the user experience. Here’s why:
- Disorientation: Scroll hijacking disrupts users’ expectations of how scrolling should work. This can cause confusion, frustration, and even disorientation.
- Loss of control: By manipulating the scroll behavior, designers take away users’ control over their browsing experience. This can lead to feelings of powerlessness and annoyance.
- Inconsistent behavior: Scroll hijacking can create inconsistent behavior across different devices and browsers, making it difficult for users to adapt.
- Accessibility issues: For users with disabilities, scroll hijacking can exacerbate existing accessibility challenges, such as difficulty navigating or understanding content.
- Negative impact on usability: Scroll hijacking can increase cognitive load, making it harder for users to focus on the content and complete their tasks.
When to Avoid Scroll Hijacking
- High-traffic sites: Avoid scroll hijacking on high-traffic sites, as it can lead to user frustration and decreased engagement.
- General audience: Don’t use scroll hijacking on sites targeting a general audience, as it may confuse or alienate users.
- Critical information: Avoid hijacking scrolling when users need to quickly access critical information, such as emergency services or important updates.
When to Consider Scroll Hijacking
- Niche audiences: If you’re targeting a niche audience familiar with innovative design patterns, scroll hijacking might be acceptable.
- Storytelling: Use scroll hijacking to guide storytelling and progressive disclosure of complex information, as long as it’s well-executed and user-friendly.
- Brand reinforcement: If you’re looking to reinforce your brand’s innovative or creative identity, scroll hijacking might be a suitable choice.
Best Practices
- Test and refine: Thoroughly test scroll hijacking designs and refine them based on user feedback.
- Provide alternatives: Offer alternative methods for users to navigate and control their scrolling experience.
- Keep it subtle: Avoid overusing scroll hijacking or making it too prominent, as this can be overwhelming.
In conclusion, while scroll hijacking can be an attention-grabbing design element, it’s essential to weigh its potential benefits against the potential harm to the user experience. By understanding the limitations and best practices, designers can use scroll hijacking effectively and respectfully, prioritizing usability and accessibility.
So this will probably not be the last issue you run into by using this thing that you do not need. Just saying.
No idea what this does and what
not responding very well on <div> containing Youtube videos embed through ARVE plugin.
Is supposed to mean. What is supposed to do? I know scroll hijacking and JS solutions are a bad idea and there is native smooth scroll, so without fully understanding this supposed very popular script I never heard of my reaction would be to just not use it and use native smooth scroll.
html {
scroll-behavior: smooth;
}This is all you need for smooth scroll these days. The link you had shows you can ignore elements from your thing with just adding a class, so you can do that. Still no clue what this thing does and why individual elements need to “respond” to anything.
I can not reproduce this. Works fine for me on multisite.
Open a support ticket at https://nextgenthemes.com/support/ fill in the debug info. Deactivate all other plugins and see it this is caused by some incompatibility. Also try a default theme so we can find out if this is caused by a conflict with some other code.
Your way hm. Yeah, shady AF as I said! Funny that you even admit this as opposed to a claim “no clue how that happened” I recently got from the SupportCandy folks, who also just marked my topic as resolved.
It says “resolved” and your shady practice is because this is how you FAKE your “resolved” topics display that is shown on your plugins page. This should be against wp.org rules.Here is how I do it. I tell people to not use this forum and use the ticketing system on my site. People love to not read or straight up ignore it. So sometimes I mark questions as “not a support question”. Because I feel it unfair how they raise the “unsolved” number that way. This way, topics get removed from the counter completely. But if you do give support here, then do not do this shady shit!