Make WordPress Themes

Opened 5 weeks ago

Closed 4 weeks ago

Last modified 4 weeks ago

#258438 closed theme (not-approved)

THEME: mosir – 1.1.1

Reported by: webbingstudio's profile webbingstudio Owned by: bijayyadav's profile bijayyadav
Priority: previously reviewed Keywords: theme-mosir accessibility-ready
Cc: services@…

Description

mosir - 1.1.1

“mosir” (mo-shi-ri) is a hybrid theme suitable for website management by organized teams. Main features: Coding with long-term operation in mind / High accessibility / Block editor support / Various navigation patterns / CSS variable management linked to “theme.json”.

Theme URL - https://mosir.webbingstudio.com/
Author URL - https://webbingstudio.com/

Trac Browser - https://themes.trac.wordpress.org/browser/mosir/1.1.1
WordPress.org - https://wordpress.org/themes/mosir/

SVN - https://themes.svn.wordpress.org/mosir/1.1.1
ZIP - https://downloads.wordpress.org/theme/mosir.1.1.1.zip?nostats=1
Live preview – https://playground.wordpress.net/#…

Diff with previous version: [314518] https://themes.trac.wordpress.org/changeset?old_path=mosir/1.1.0&new_path=mosir/1.1.1

History:

Ticket Summary Status Resolution Owner
#257185 THEME: mosir – 1.1.0 closed not-approved ammarsaif
#258438 THEME: mosir – 1.1.1 closed not-approved bijayyadav

(this ticket)


https://themes.svn.wordpress.org/mosir/1.1.1/screenshot.png
Theme Check Results:

  • RECOMMENDED: No reference to register_block_pattern was found in the theme. Theme authors are encouraged to implement custom block patterns as a transition to block themes.
  • RECOMMENDED: No reference to register_block_style was found in the theme. Theme authors are encouraged to implement new block styles as a transition to block themes.
  • WARNING: Could not find a copyright notice for the theme. A copyright notice is needed if your theme is licenced as GPL. <a href="https://www.gnu.org/licenses/gpl-howto.html" target="_blank">Learn how to add a copyright notice (opens in a new window).</a>
  • WARNING: assets/images/home/mv_default_2to3.jpg is 591.4 KB in size. Large file sizes have a negative impact on website performance and loading time. Compress images before using them.
  • WARNING: screenshot.png is 516.4 KB in size. Large file sizes have a negative impact on website performance and loading time. Compress images before using them.
  • RECOMMENDED .sticky css class is recommended in your theme css.
  • RECOMMENDED .bypostauthor css class is recommended in your theme css.
  • RECOMMENDED .alignleft css class is recommended in your theme css.
  • RECOMMENDED .alignright css class is recommended in your theme css.
  • RECOMMENDED .aligncenter css class is recommended in your theme css.
  • RECOMMENDED .wp-caption css class is recommended in your theme css.
  • RECOMMENDED .wp-caption-text css class is recommended in your theme css.
  • RECOMMENDED .gallery-caption css class is recommended in your theme css.
  • RECOMMENDED: No reference to add_theme_support( "custom-header", $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
  • RECOMMENDED: No reference to add_theme_support( "custom-background", $args ) was found in the theme. If the theme uses background images or solid colors for the background, then it is recommended that the theme implement this functionality.

Change History (4)

#1 @webbingstudio
5 weeks ago

I will correct the parts that I think caused the rejection and resubmit. Thank you in advance.

  • Redefined the image size for the_post_thumbnail() specifically for the theme.
  • Added prefixes to the CSS and JS enqueue IDs.
  • Fixed missing translations for the previous and next links on the post details page.
  • Unable to reduce the file size of screenshot.png any further.

#2 @bijayyadav
4 weeks ago

  • Owner set to bijayyadav
  • Status changed from new to reviewing

#3 @bijayyadav
4 weeks ago

  • Resolution set to not-approved
  • Status changed from reviewing to closed

Hi @webbingstudio,

Thank you for submitting your theme. I have had a quick look, and at this point, it does not fully meet the WordPress.org Theme Review requirements. Please review the requirements carefully, fix the issues, and upload a new version for review.

The Theme Review Team does not hard reject themes — we want you to resubmit your theme. However, when a ticket is closed as not approved, it loses its position in the review queue. When you submit an update, a new ticket will be created at the end of the queue.

If any requirements are unclear, please let us know so we can continue to improve them. For reference, you may find these resources helpful:
https://make.wordpress.org/themes/handbook/review/required/

https://make.wordpress.org/themes/handbook/review/how-to-do-a-review-draft/

https://github.com/WPTRT/theme-sniffer/

Use this upload form to submit your update: ​https://wordpress.org/themes/upload/


  • Your theme includes the accessibility-ready tag. Please note that an accessibility-ready review is a separate process and will take additional time. If you do not want to wait for a separate accessibility review, kindly remove the tag from your theme.
  • Any data retrieved from the database must be sanitized on input and escaped on output. Please ensure proper escaping is applied before displaying it on the front end. Eg. single.php line no. 44
  • All the text strings in the PHP file should be translation-ready. Eg. single.php line no. 44.
  • The wp_footer() function should be placed immediately before closing </body> tag.

+ possibly more issues.

Thank you

#4 @webbingstudio
4 weeks ago

@bijayyadav
Thank you for letting me know the reason in detail. I will withdraw my application and reconsider the theme. Thank you.

Note: See TracTickets for help on using tickets.