Corey Salzano
Forum Replies Created
-
Forum: Plugins
In reply to: [HEIC Support] HEIC supported but unable to uploadHi Chris,
Thanks for trying my plugin. There must be some restrictions by your host or another plugin. All of these file extensions can be uploaded and converted to .jpg without the HEIC Support plugin and without your code snippet since WordPress 6.7.
So, the only reason you may need this plugin in 2026 is if some other code or server configuration disables this features: https://make.ww.wp.xz.cn/core/2024/08/15/automatic-conversion-of-heic-images-to-jpeg-in-wordpress-6-7/
I am open to adding similar code to the plugin, and I appreciate the feedback.Forum: Plugins
In reply to: [HEIC Support] Images uploading but not converting to JPGHi Miguel,
Thanks for trying my plugin. This is not enough information to help. I just tested a conversion, and the plugin is working for me. What settings are you using at Settings > Media > HEIC Support? JPG and replacements on or off?Thanks for trying the plugin! When I go to this page, I see a vehicle: https://kkers.com/inventory I think your second test vehicle is either a Draft or Trashed.
I don’t see the full post content, so I doubt the display conditions for the Divi template that contains the module in your screenshot are enabled for Vehicles Archive Page. The display conditions are what link your configuration in Divi theme builder to the front-end pages. Revisit step 5 of this page https://inventorypresser.com/docs/divi-setup-guide/ for which checkboxes to choose for the two templates.Thanks for the update!
No, there are no unlisted features of this plugin. I would handle bulk conversions with shell scripting and SSH access to the server with something like this…
for file in *.heic; do
magick "$file" "${file%.heic}.jpg"
done…and the
wp media importcommand create Media Library items.Forum: Plugins
In reply to: [Power Boost for Gravity Forms] Unstyled id’sThanks for trying my plugin, and thanks for this feedback. I just published version 3.2.3 that fixes the CSS issues. Duplicate IDs sometimes show in Compact mode until a page refresh. If that is not your experience, let me hear from you again.
Thanks again
Thanks for trying my plugin. I haven’t received any other reports of the options-media page breaking when running this plugin. I don’t know if the plugin requires PHP8. Are you getting an error message you can share?
Hi,
Thanks for trying my plugin. If you’ve improved the code, send a pull request! https://github.com/csalzano/heic-support/
I don’t use this plugin. I don’t know why anyone still needs this plugin since the feature was built into core last year https://make.ww.wp.xz.cn/core/2024/08/15/automatic-conversion-of-heic-images-to-jpeg-in-wordpress-6-7/
I don’t mind maintaining it, but have you tried deactivating HEIC Support and trying an .heic upload since updating to WordPress 6.7?
Thanks again.
Hi, thanks for trying my plugin. Please try viewing the Settings → Media → HEIC Support section after updating to the latest version, 2.1.4. You may not have seen the settings previously.
Forum: Plugins
In reply to: [HEIC Support] Settings are missing in Settings->MediaHi, thanks for trying my plugin. I found out how to reproduce this problem, and I fixed it in version 2.1.4. Thanks for reporting a bug, and let me know if you still do not see the settings after updating.
Forum: Plugins
In reply to: [HEIC Support] GD instead ImageMagickHello. Thanks for trying my plugin. I have not used GD in a project yet, but I will take a look and consider using it as a fall-back when imagemagick is not installed. Thanks again.
I don’t believe there is a problem with the spinner. I see a green “Feeds were resent successfully” message. If the feed crashes during the re-run, the spinner might spin indefinitely. Enable debugging and see if a fatal error is written while rerunning the feed. I’m marking this resolved because this is expected behavior.
Hi, thanks for trying my plugin!
The string “inputType” does not appear in this plugin, so it’s not something I’m trying to do.
I can reproduce your test. I see the
inputTypeattributes on fields appearing. The method that’s doing it isGFAPI::update_form(). That’s in Gravity Forms. I’m calling during the .json Load button click. TheinputTypeattribute is showing up in your .json file after a form change is detected during the load.The Forms > Import Export > Export Forms feature creates .json without these attributes, but once they are added, they persist. More research is necessary on this one. Thanks for the tip.
Forum: Plugins
In reply to: [Meow Lightbox] MeowCommon_Admin is called too earlyPlease fix this. The constructor of your
MeowCommon_Adminclass is calling$this->is_user_admin()on line 53 and causing this log message during every admin page load.There are 5
error_log()calls in your plugin. Delete them all please. We can’t act on any of this information. One of them is inside a function calledtimer_log_elapsed()that your plugin never seems to use. There’s lots of code in comments. Please make all our sites faster by deleting every extra line in every file.Forum: Plugins
In reply to: [Power Boost for Gravity Forms] Json import issuesHi Pawel,
We communicated outside this forum, and I appreciate your help in preparing version 3.2.0 to accommodate plugins like GravityFlow that insert their feed settings into form export files. Version 3.2.0 is available on Github today and will reach all users via .org soon.
Thanks
Well, I need it to help one of our mutual customers make money & continue paying for their Dokan Pro license. I’m a contractor trying to customize Dokan’s interfaces.
Also, the plugin review team now requires it. Here’s an excerpt I got from [email protected] earlier this year:
## No publicly documented resource for your compressed content
In reviewing your plugin, we cannot find a non-compiled version of your javascript and/or css related source code.
In order to comply with our guidelines of human-readable code, we require you to include a link to the non-compressed, developer libraries you’ve included in your plugin. This may be in your source code, however we require you to also have it in your readme.
We strongly feel that one of the strengths of open source is the ability to review, observe, and adapt code. By maintaining a public directory of freely available code, we encourage and welcome future developers to engage with WordPress and push it forward.
That said, with the advent of larger and larger plugins using more complex libraries, people are making good use of build tools (such as composer or npm) to generate their distributed production code. In order to balance the need to keep plugin sizes smaller while still encouraging open source development, we require plugins to make the source code to any compressed files available to the public in an easy to find location, by documenting it in the readme.
For example, if you’ve made a Gutenberg plugin and used npm and webpack to compress and minify it, you must either include the source code within the published plugin or provide access to a public maintained source that can be reviewed, studied, and yes, forked.
We strongly recommend you include directions on the use of any build tools to encourage future developers.
I think Github or Bitbucket would be a great place to provide unminimized files for developers like me. You can continue shipping the plugin with the smaller file size.
- This reply was modified 1 year, 8 months ago by Corey Salzano.