My plugins have been disabled for almost a day due to prettyphoto vulnerability. I have submitted the files again for review however its taking a lot more time than usual, almost 23 hours now. Can you please take a look since our plugin does NOT include prettyphoto files nor use them. We just check for the existence of $.fn.prettyPhoto so that we can add CSS classes for prettyPhoto effect.
By the way, we did re-submit the plugins after the vulnerabilities were found but did no upload any new package files, since we had no files to change in the current package.
Can you please consider:
- Creating a dedicated tab for the FAQ page
- Make the title of each FAQ bigger. Why is it so small now (14px)? We use h4 tags in our FAQs and that is already 16px in size and it is making FAQs very unreadable.
- Create table of contents for FAQs. We have more than 50 FAQs and we do not want users to having to read all FAQs to find a solution for their issues.
The FAQs section needs a table of contents at the top. I have 50 FAQs in one of my plugins and users will need to scroll down the whole page and read them all to find what they are looking for.
Another suggestion is to make the FAQ title larger! It was a lot more readable before the redesign. Currently it is really hard to differentiate the FAQ title and its content.
Why can’t we have a dedicated FAQs tab? Many users don’t realize there are FAQs under the Support tab, and since now only top FAQs are displayed, we are receiving a lot more questions that have already been answered in the FAQs, than it was before the redesign.
To get around this, we’d need a major/minor versioning system – major for value-add updates (possibly paid) and minor for basic/security patch updates (possibly unpaid) – this would add a lot of complexity and considering that authors update in very different ways would be hard to manage.
It will not be complex as you think if both updates are provided to valid license holders only. You can build a more sophisticated system like you mentioned in the future if buyers/authors really need that kind of system. However even with that kind of system, most authors will not provide security patches for every x.x.x version they have released because of their limited resources (manpower and time). They will most likely to tell the buyers to update their files to the latest version.
Having the same issue here. The button turns into “Processing…” and stops there.
I am also having the same issue for several weeks now.