joppuyo

Hello!

This plugin does not change your file names, it only changes the post slug that is stored in the database. WordPress stores attachments in the same database table as pages and they have a slug just like pages. If you upload a file called example.jpeg, WordPress reserves the slug “example” for the attachment page. If you then create a page called “Example”, the slug for that will be “example-2” because the attachment has reserved the slug “example”.

This plugin fixes that by changing the attachment slugs to something like “d41a82e25534412fa2838aee5bf05e53” so they cannot reserve slugs from pages. However, this happens only for attachments uploaded after the plugin has been installed.

The “mangling” tool allows you to retroactively change the slugs to random ones for existing files so they won’t cause slug conflicts with pages in the future.

I hope this clears things up!

Hello!

I don’t use Elementor and I’m not able to help and debug with any kinds of custom integrations.

This plugin is intended to be used with Advanced Custom Fields and ACF Forms. Any other plugins and integrations are unfortunately out of scope.

If you are having problems with Elementor, I suggest contacting Elementor support.

This issue has been addressed in version v3.1.1 of the plugin which was just released on the plugin directory.

Hello! This plugin does not prevent users from accessing files in the upload directory using a direct link. It only disables a WordPress feature called “attachment pages”. These are HTML pages that contain an embedded version of the media file. Main purpose of this plugin is to prevent search engines from indexing these “attachment pages”. If you want to prevent users from accessing media files directly, you will need to use a different plugin, for example this one:

https://preventdirectaccess.com/

Hello! I’m currently not planning on adding a support for galleries and I suggest to use a repeater instead. Data from the repeater can be accessed using standard ACF functions, such as get_field.

This plugin doesn’t provide any kind of Elementor compatibility. Please contact Elementor support if you have questions about their ACF integration. They may be able to provide code that works in your use case.

Hello!

I am not familiar with using a 410 status code. Are there some articles or documentation pages that recommend using this code over 404?

If so, I might consider adding a filter that allows you to customize the status code the plugin returns.

Hello! This plugin is intended for use cases where the image aspect ratio has to match exactly to a certain element in the page template. This is why cropping is mandatory. I’m not planning on adding a feature where cropping would be optional as this is not the intention behind the plugin.

• This reply was modified 1 year, 1 month ago by joppuyo.

Hello! Thank you for your kind words!

When it comes to your feature request, I’m not planning on adding this feature as it runs contrary to the intention of the plugin. The idea is that the plugin provides an image that is always in the correct aspect ratio. If I would add a feature that allows bypassing the cropping, you could no longer be sure that the images are in the right aspect ratio.

However, there’s already a feature in this plugin that bypasses the cropping if the image matches the aspect ratio exactly or almost exactly. How this works is that you can simply leave the default crop crosshair as-is and click the crop button. The plugin will not create and additional image if the aspect ratio is a match.

I hope this answers your question!

I’m not sure if I understand the issue. The image crop field can be placed inside a repeater without an issue. But I don’t know what you mean by “Snipping”. Maybe you could include a screenshot to demonstrate the issue more clearly?

Hello! The current version of the plugin is minimally maintained until the next major version of the plugin is released.

My aim is that the current plugin version works with latest version of ACF 5 and WordPress. If there are any bugs with this compatibility, I will do my best to fix them.

I use this plugin personally on several sites and I don’t plan on abandoning it. However, I don’t plan supporting ACF6 in the current version of the plugin because I’m working on the next major version of the plugin which is a partial rewrite.

I hope this clears up the current situation!

Nice! I’m closing this thread as resolved.

Hello, this plugin does not collect or store any personal data so therefore it is GDPR compatible.

Yes, I realized that it’s possible to uncheck those themes and plugins I don’t need, which dramatically improved the performance.

The options were a bit hard to find because it is named “Export/import translations”. I would suggest perhaps renaming this to something like “Theme and plugin translation” or similar. It would be nice also to mention this feature in the documentation.

Anyway, thanks for the great work on the plugin. It would be nice if some of my suggestions could be taken into account in future versions so more people can benefit from improved performance.

Hello! I’m sorry you had a bad experience with the plugin. This sort of thing should not happen because the plugin does not modify the database in any way. I have used this plugin on dozens of sites without any issues. You should be able to get back Customizer by simply disabling the plugin.

Despite this, it’s always possible that there are compatibility issues with other plugins or other bugs. If you submit a detailed bug report I might be able to troubleshoot the issue and potentially release a fix in the plugin.

Closing as this feature is not planned and a workaround has been provided.