[theme-reviewers] Why the double standards and why Pagelines gets special treatment?

Satish Gandham satish.iitg at gmail.com
Fri Mar 23 18:40:58 UTC 2012

Pagelines themes always get special treatment, last time when i raised this
point it was buried saying it was only a human error and there is no
special treatment or favoritism. This happened again

1. Theme upload to the repository fails if it doesn't use add_theme_page()
for adding admin pages. Yet pagelines somehow bypases this restriction,
escapes the reviews eyes and makes it to the featured list.

2. For my theme removing the default fav icon was a requirement, but for
page lines they add their logo as favicon, set their logo for the site logo
by default. include their logo in the footer with any option to remove it.

3. They up-sell the page lines theme, their premium version has to be fully
gpl, yet you find this on their site.

"Can I use PageLines on more than one site?
If you own the PageLines Professional Edition you can use it on multiple
sites owned by you or your organization.
If you own the PageLines Developer Edition you can use it to build an
unlimited number of sites for yourself or for others."

You don't even care to check these while adding it to featured themes list,
yet you take special interest in digging into my site to find faults with
my theme and license.

4. They are allowed to hotlink images, while other aren't

5. While other themes must save all the theme options in a single array,
pagelines can have 5 db entries.
6. They bundle their store script along with the theme, how can that be a
part of the theme?

Why this favoritism and why this double standards?
Why this favoritism and why this double standards?
Why this favoritism and why this double standards?

*****Points from theme review guidelines*********

   - Themes are *required* to include within the Theme all images, scripts,
   and other bundled resources. Such resources *must not* be "hotlinked"
   from a third-party site.
   - Themes are *recommended not* to implement custom favicon
   functionality. If implemented, favicon functionality is *required* to be
   opt-in, and disabled by default.
   - Themes are *required* to use the *add_theme_page()* function to add
   the Theme Settings Page to the *Appearance* menu, rather than using *
   add_menu_page()* to add a top-level menu.
   - Themes are *required* to save options in a single array, rather than
   create multiple options for its settings page. Use of set_theme_mod and
   get_theme_mod handles this for you, as does using the Settings API.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20120324/9607252e/attachment.htm>

More information about the theme-reviewers mailing list