lhalda

Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)

  • Never mind, I have transferred all the functionality to a Advanced Custom Fields field and disabled WP Subtitle so there’s no conflict anymore ??

    sql formatting misformatted the code tag, stripping backquotes (can’t edit again for some reason):

    INSERT INTO wp_postmeta (meta_id, post_id, meta_key, meta_value) VALUES
(9993, 317, 'wps_subtitlewps_subtitle', ''),
(9994, 317, '_wps_subtitlewps_subtitle', 'field_57fe080bee162');

    Hello, I’m getting this problem as well, with a few differences:

    Apparently, the subtitle saves as Unicode text but loads to page edit in administration in some other encoding (I’d guess Windows-1252). Also, this is how it works in my user account with all privileges, but in the actual admin account, it also appends a custom field called wps_subtitle, where it shows right, and changes don’t matter when saving the page.

    It’s breaking our workflow, do you have any suggestion how to correct it? Do you need more information, and what kind? Can I help debugging?

    WordPress 4.6.1 (Czech), activated plugins Advanced Custom Fields 4.4.10, Google Analytics 1.0.6, PixelYourSite 4.0.0, PlanSo Forms 2.5.5, WP Subtitle 2.8.1, WPBruiser 3.0.15

    I suspect the problem is caused by conflict with updated Advanced Custom Fields – in database in wp_postmeta table are added these lines we don’t want:

    INSERT INTOwp_postmeta(meta_id,post_id,meta_key,meta_value`) VALUES
    (9993, 317, ‘wps_subtitlewps_subtitle’, ”),
    (9994, 317, ‘_wps_subtitlewps_subtitle’, ‘field_57fe080bee162’);`

    • This reply was modified 8 years, 1 month ago by lhalda.
Viewing 3 replies - 1 through 3 (of 3 total)