aliyaghobi
کاربر عضو
سلام دوستان
یک افزونه کوتاه کننده لینک را که سایت سرویس دهیش از دسترس خارج شده را از مخزن وردپرس دانلود کردم. فارسی سازیش کردم و از سرویس سایت
و افزونه ای که من فارسی سازیش کردم
برای ثبت در مخزن برای وردپرس ارسال کردم و همچین ایمیلی برام ارسال کردند. میشه لطف کنید کمکم کنید تا مشکل را رفع کنم تا تو مخزن منتشر بشه
منتظر پاسخ شما هستم
سپاس
یک افزونه کوتاه کننده لینک را که سایت سرویس دهیش از دسترس خارج شده را از مخزن وردپرس دانلود کردم. فارسی سازیش کردم و از سرویس سایت
لینک ها تنها برای اعضای سایت قابل نمایش است.
استفاده کردم.
لینک ها تنها برای اعضای سایت قابل نمایش است.
و افزونه ای که من فارسی سازیش کردم
لینک ها تنها برای اعضای سایت قابل نمایش است.
برای ثبت در مخزن برای وردپرس ارسال کردم و همچین ایمیلی برام ارسال کردند. میشه لطف کنید کمکم کنید تا مشکل را رفع کنم تا تو مخزن منتشر بشه
There are issues with your plugin code.
Please read this ENTIRE email, address all listed issues, and reply to this email with your corrected code attached. It is required for you to read and reply to these emails, and failure to do so will result in significant delays with your plugin being accepted.
Also please remember in addition to code quality, security and functionality, we require all plugins adhere to our guidelines. If you have not yet, please read them:
*
لینک ها تنها برای اعضای سایت قابل نمایش است.
## Calling files remotely
Offloading images, js, css, cgi, and other scripts to Google (or jquery.com or anywhere else frankly) is disallowed because you're introducing an unnecessary dependency on another site. If the file you're trying to use isn't a part of WordPress Core, then you should include it -locally- in your plugin, not remotely. If the file IS included in WordPress core, please call that instead.
The one exception to this rule is if your plugin is performing a service. We will permit this on a case by case basis, however since this can be confusing, we have some examples of what are not permitted:
* Offloading jquery CSS files to Google - You should include the CSS in your plugin.
* Inserting an iframe with a help doc - A link, or including the docs in your plugin is preferred.
* Calling images from your own domain - They should be included in your plugin.
* Inserting an iframe with a help doc - A link, or including the docs in your plugin is preferred.
* Calling images from your own domain - They should be included in your plugin.
Here are some examples of what we would permit:
* Calling font families from Google or their approved CDN (if GPL compatible)
* API calls back to your server to process possible spam comments (like Akismet)
* Offloading comments to your own servers (like Disqus)
* oEmbed calls to a service provider (like Twitter or YouTube)
* API calls back to your server to process possible spam comments (like Akismet)
* Offloading comments to your own servers (like Disqus)
* oEmbed calls to a service provider (like Twitter or YouTube)
Please remove this dependency from your plugin and, if possible, include all files within the plugin (that is not called remotely). If instead you feel you ARE providing a service, please re-write your readme.txt in a manner that explains the service, the servers being called, and if any account is needed to connect.
Examples:
wp_enqueue_script('plink-table','//cdn.datatables.net/1.10.4/js/jquery.dataTables.min.js',array('jquery'));
wp_enqueue_style('plink-table','//cdn.datatables.net/1.10.4/css/jquery.dataTables.min.css');
wp_enqueue_style('plink-table','//cdn.datatables.net/1.10.4/css/jquery.dataTables.min.css');
## Generic function (and/or define) names
All plugins must have unique function names, defines, and classnames. This prevents your plugin from conflicting with other plugins or themes.
For example, if your plugin is called "Easy Custom Post Types", then you might prefix your functions with ecpt_{your function name here}. Similarly a define of LICENSE would be better done as ECPT_LICENSE. You can use namespaces instead, however make sure that those also are unique. A namespace or class of 'MyPlugin' is NOT actually all that unique.
This extends to anything in a define. For example, if you were to use this, it would be a bad idea:
define( 'PLUGIN_PATH', plugins_url( __FILE__ ) );
That define is a global, so PLUGIN_PATH could conflict with a number of other things.
Don't try to use two letter slugs anymore. As of 2016, all the good ones are taken. Instead consider easy_cpts_ (from the first example).
Similarly, don't use __ (double underscores), wp_ , or _ (single underscore) as a prefix. Those are reserved for WordPress itself. You can use them inside your classes, but not as stand-alone function.
Please update your plugin to use more unique function and class names.
Some examples from your plugin:
function shortlink_create_menu()
function register_mysettings()
function short_link_settings_page()
function wan_load_textdomain()
function register_mysettings()
function short_link_settings_page()
function wan_load_textdomain()
If those are intended to be in shared libraries, please detect IF the code is already included and not re-include it, as doing so will cause conflicts if two people call the same defines and functions.
Please make sure you've addressed ALL issues brought up in this email. When you've corrected your code, reply to this email with the updated code attached as a zip, or provide a link to the new code for us to review. If you have questions, concerns, or need clarification, please reply to this email and just ask us.
Please make sure you've addressed ALL issues brought up in this email. When you've corrected your code, reply to this email with the updated code attached as a zip, or provide a link to the new code for us to review. If you have questions, concerns, or need clarification, please reply to this email and just ask us.
(While we have tried to make this review as exhaustive as possible we, like you, are humans and may have missed things. As such, we will re-review the ENTIRE plugin when you send it back to us. We appreciate your patience and understanding in this.)
منتظر پاسخ شما هستم
سپاس
