alleknalle

Hi Iulia,

Thank you for answering my questions and thank you for creating this plugin ??

I found out how it works. There are two options:

• Set at least one size to ‘global ignore’
• Set at least one size to ‘unavailable’

When you do one of the two things listed above, all the other sizes will be selectable in the dropdowns for selecting image sizes. Note: still only sizes that are available for the specific image are selectable.

Now I’ve got multiple questions:

• Wouldn’t it be easier to add a checkbox where people can select which sizes will be shown? This is how it’s done in Simple Image Sizes and is, in my opinion, a lot more logical.

• What is the difference between ‘hide’ and ‘unavailable’ for a specific size? And why does the showing of image sizes only works when you set at least one size to ‘unavailable’ and not when you set at least one size to ‘hide’?

Look like it works now, thanks ??

Great, good to hear. I just think that you forgot to update version number, so now the plugin is not updating ??

Hi @hjogiupdraftplus ,

Just tested it and it works ?? Nice to see the addition that it checks if the constant is defined ??

Thanks for the fix!

Thanks, looking forward hearing from you soon ??

Hi @hjogiupdraftplus ,

Thanks for your reply ??

DISALLOW_FILE_EDIT constant is added to wp-config.php by AIOS when you enable the setting ‘Disallow file edits’. That’s fine.

The ‘issue’ is that it is added totally at the bottom of wp-config.php. This means that it is added after require_once ABSPATH . 'wp-settings.php';

If any other plugin/theme defines DISALLOW_FILE_EDIT somewhere in the code then there will be a PHP warning stating that DISALLOW_FILE_EDIT is already defined.

According to the wp-config.php file, there is a place in that file to add custom values. That is BEFORE ABSPATH is being defined. I think that would be a better place to define DISALLOW_FILE_EDIT.

Since AIOS is also adding things to the top of wp-config.php (to include aios-bootstrap.php for the firewall), I think the top of wp-config.php would also be fine to define DISALLOW_FILE_EDIT.

Another solution would be to add a check if it’s already defined before defining DISALLOW_FILE_EDIT. That would also stop any warnings to occur if the constant is already defined somewhere else.

Hope I made my issue (and the possible solutions) clear ??

Hi Reüel,
can’t get it working. When I place my .mo/.po files in /wp-content/languages/plugins/ folder, it doesn’t ‘overwrite’ the translations from woocommerce-nl in /wp-content/plugins/woocommerce-nl/languages/woocommerce/.
So I have:
/wp-content/languages/plugins/woocommerce-nl_NL.mo
/wp-content/languages/plugins/woocommerce-nl_NL.po
/wp-content/plugins/woocommerce-nl/languages/woocommerce/nl_NL.mo
/wp-content/plugins/woocommerce-nl/languages/woocommerce/nl_NL.po

/wp-content/languages/plugins/woocommerce-nl_NL.mo should overwrite translations done in /wp-content/plugins/woocommerce-nl/languages/woocommerce/nl_NL.mo right?