Forum Replies Created

Viewing 15 replies - 1 through 15 (of 73 total)
  • Thread Starter julia77

    (@julia77)

    Hello,

    I want to exclude several form widgets from translation. I′m using Pro version. Anyway, is there a way to exclude any other widget included in the free version from translation to default language?

    [ redundant link removed ]

    Thanks

    • This reply was modified 2 years, 10 months ago by julia77.
    Thread Starter julia77

    (@julia77)

    Hello,

    Post are manually translated since the plugin I used for translating usually broke html (Hello theme). That′s what I′m searching for a snippet to only exclude some Elementor’s form fields from string translation.

    Thread Starter julia77

    (@julia77)

    I had to remove it since css was not displayed even after unchecking minify/combine css options, and clearing/deleting caches (WordPress, several browsers, no cache on server side).

    It was functioning pretty well even without CDN and in a shared hosting. No new plugins′s been added, the site always functioning with the same and lastest WordPress, theme and plugins versions (Elementor, NinjaFirewall, SEO Simple Pack and other minor plugins to log in, remove categories from url, hide notices in WordPress Admin dashboard, and prevent antispam in comments form), so I cannot tell what happened (stylesheets were loaded, as seen in the inspector).

    Performance was good!

    Thread Starter julia77

    (@julia77)

    Thanks

    Thread Starter julia77

    (@julia77)

    Thanks

    Thread Starter julia77

    (@julia77)

    Yes! In Pages/Posts section in WordPress (and in preview mode)

    Thread Starter julia77

    (@julia77)

    Hi Emre,

    Just left a good review, thanks

    Thread Starter julia77

    (@julia77)

    Thanks

    Thread Starter julia77

    (@julia77)

    I will suggest this, thanks for the link.

    Kudos to you and best of luck with the project

    What is kudos? What project?

    Thread Starter julia77

    (@julia77)

    Finally, I did it manually, directly editing each row in the table in phpMyAdmin. And checked with Broken Link Checker plugin.

    Thanks @soberbanda for your answers!!

    Since that table uses to be so big, and most users just upload and delete and change themes/media sizes and reload and change again, etc. sooo often …could someone at WordPress just give a customizable function to handle data in that table? Specifically for images …I′m using a filter to prevent storing exif and iptc metadata in the same meta key for sizes:

    add_filter( ‘wp_read_image_metadata’, ‘__return_false’ );

    but I had to delete manually all data that was added previously by default …

    I guess wp-includes/media.php points something about this but I have no idea about serializing, unserializing, filtering results, deleting specific data, serializing again and restoring to db …I′m affraid this tasks have to be done manually by users like me …??

    • This reply was modified 3 years, 1 month ago by julia77.
    • This reply was modified 3 years, 1 month ago by julia77.
    Thread Starter julia77

    (@julia77)

    Hi @soberbanda,

    I have my wp_postmeta table ready to replace the old one. Before that, I`ve activated the free version of Media Cleaner plugin to see settings and options to run after replacing the table. Unfortunately, the plugin says that additional checks are required to scan posts/pages built with Elementor (that′s the builder on my entire website).

    Would you recommend any other way to check for errors in images′ displaying before deleting the unused sizes?

    Thread Starter julia77

    (@julia77)

    Just one question about replacing a WordPress table in database: I′ve downloaded wp_postmeta table in a PHP file format. After modifying data, should I just delete the table in db and then upload the modified data in the same file format?

    I′ve never deleted or replaced a WordPress table in db before

    Thread Starter julia77

    (@julia77)

    About the remove_filter directive, I don′t understand either how it prevents WordPress from generating those hughe images. All I know is that they′re not being generated since then…as there′s no option in the Admin panel to unset them, I guess that directive is working somehow …

    I′m about to delete images′ sizes metadata manually via exporting/importing a query for only _wp_attachment_metadata meta_key in wp_postmeta table (not the whole table or db).

    After that, then I can delete unused images′ sizes without deleting the ones being currently displayed on the site, right?

    Thread Starter julia77

    (@julia77)

    Hello @soberbanda,

    I′ve started a topic in Regenerate thumbnails plugin′s support forum to check if old images sizes are deleted when regenerating according to new settings in WordPress Administration Screen, and to know what happens to old metadata stored in db. When I get an answer, I′ll post it in here.

    In that forum, I′ve also read that other people deleted unused images directly from the server. And even after regenerating with the plugin, metadata in db remained as before and images on the website were not properly displayed (metadata was pointing to images that no longer existed). That happened to me years ago, as I mentioned when started this topic.

    In the thread you provided, they say:

    – Size data in WordPress is stored as a serialized array.
    – Convert data to normal arrays and back to serialized automatically.
    – Query results in PHP to get metadata where the meta_value has a string like one of the size names you want to delete.
    – Step through the records and unset the undesired size elements.
    – Save the modified array back to the DB.

    I have no idea how to do this, I just found the code mentioned at the beginning of this topic.

    About applying filters when uploading images, I′m currently using this line in functions.php file, specifically for the new hughes sizes since one of the latest WordPress update. When combined with values set in the Administration Screen, it works fine up to now:

    remove_filter( ‘wp_robots’, ‘wp_robots_max_image_preview_large’ );

    Which is the difference with your code?

    `add_filter( ‘intermediate_image_sizes_advanced’, ‘wpse_240765_image_sizes’ );

    function wpse_240765_image_sizes( $sizes ){
    $sizes = array();
    return $sizes;
    }

    In here, I′ve found your code with parameters:

    apply_filters( ‘intermediate_image_sizes_advanced’, array $new_sizes, array $image_meta, int $attachment_id )

    Regards,

    Julia

    Thread Starter julia77

    (@julia77)

    Ok!

Viewing 15 replies - 1 through 15 (of 73 total)