Theme disapproved on Theme Repository

  • StuckOnSEO

    (@stuckonseo)


    14 years, 8 months ago

    I’ve submitted a theme to the theme repository and have it disapproved by chipbennett with the comments that the Author URL and the Theme URL are not appropriate, and that these were issues from a previous ticket – yet previous tickets didn’t mention this as being an issue, so I think there’s been some mistake.

    The first time the theme was refused was because of the footer anchor text and link, which was amended. Can someone throw some light on this, or explain how I can pass comments onto the trac system?

    The Trac reference is 5076.

    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • Moderator Ipstenu (Mika Epstein)

    (@ipstenu)

    🏳️‍🌈 Advisor and Activist

    14 years, 8 months ago

    StuckOnSEO you need to ask at http://lists.wordpress.org/mailman/listinfo/theme-reviewers for that one.

    Thread Starter StuckOnSEO

    (@stuckonseo)

    14 years, 8 months ago

    I did that and just had a bit of a telling off for using the list 🙁

    They said I need to post any feedback in the ticket system, but I can’t log in to that. It says to use the same login as WordPress.org (the one I’ve used here I should imagine) but that doesn’t work. I can’t login.

    I’m not too sure about the feeback I’ve had that reads:

    AuthorURI is a “personal accountancy” site
    ThemeURI is a news/blog post about the Theme on the same site, that has only a brief, two-paragraph description of the Theme. This is a subjective determination, but given the nature of AuthorURI, you have a higher-than-normal standard of appropriateness to meet with ThemeURI.

    “higher-than-normal standard of appropriateness to meet” is the bit that I’m unclear on. Do I take that I need to make the page for the theme more relevant than most theme pages would otherwise be? I can remove the author URL if that would help – it’s not important really.

    esmi

    (@esmi)

    14 years, 8 months ago

    yet previous tickets didn’t mention this as being an issue, so I think there’s been some mistake.

    I seriously doubt that it’s a mistake. An initial (or even a secondary) review may stop at a certain point because of a major issue. The reviewer may not go on to locate & list any other issues – not least due to lack of time and a very high workload. Ideally, it’s is the developer’s responsibility to ensure that the theme complies with all requirements – not the reviewers. S/he merely checks that it does (and that’s still a big job).

    They said I need to post any feedback in the ticket system, but I can’t log in to that.

    You should be able to use the same login credentials as you do for this forum. It’s always worked for me.

    Right now your theme is being rejected because you have links in the footer that go to an accountancy site. The theme URI is supposed to go to a page that is specifically for the theme and that might list support options or FAQS etc. The Author URI is supposed to be to a personal site. Right now, your links do neither. They both go to an apparently unrelated accountancy site rather than, say, your own site – http://www.stuckonseo.co.uk/

    That makes them look like spam links and there’s no way your theme will get accepted under those conditions.

    Chip Bennett

    (@chipbennett)

    14 years, 8 months ago

    @stuckonseo:

    I did that and just had a bit of a telling off for using the list 🙁

    The issue isn’t that you used the list (it’s there to be used, after all), but for using it out of order. In-ticket issues should only be escalated to the mail list once they are unable to be resolved in-ticket.

    The first, best, most-efficient place to post review-specific comments and questions is in the Trac ticket. Taking such comments and questions to the mail list before attempting to hash them out in-ticket would become a bit annoying and noisy for the rest of the list subscribers.

    They said I need to post any feedback in the ticket system, but I can’t log in to that. It says to use the same login as WordPress.org (the one I’ve used here I should imagine) but that doesn’t work. I can’t login.

    Now this would be an appropriate issue to raise to the mail-list – so that the appropriate people who support the WPTRT will see it, and can help you resolve your login issues.

    I’m not too sure about the feeback I’ve had that reads:

    AuthorURI is a “personal accountancy” site
    ThemeURI is a news/blog post about the Theme on the same site, that has only a brief, two-paragraph description of the Theme. This is a subjective determination, but given the nature of AuthorURI, you have a higher-than-normal standard of appropriateness to meet with ThemeURI.

    “higher-than-normal standard of appropriateness to meet” is the bit that I’m unclear on. Do I take that I need to make the page for the theme more relevant than most theme pages would otherwise be? I can remove the author URL if that would help – it’s not important really.

    Perhaps I didn’t explain that as well as I could. The underlying issue is the content of the domain, which is not a personal site, and is a commercial site entirely unaffiliated with WordPress Themes or development.

    Even on the indicated ThemeURI, the overwhelming preponderance of content involves not the Theme, but the “personal accountancy” services being offered by the domain. To be appropriate, that overwhelming preponderance needs to be exactly opposite, in favor of the WordPress Theme.

    The reason we have to maintain such strict guidelines in this regard is that the WPORG Theme Repository is an incredibly rich, tempting target for SEO/spammers who submit Themes simply to try to get the benefit of backlinks. So, in fairness to all, the credit link guidelines are very specific and strict.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Theme disapproved on Theme Repository’ is closed to new replies.