• Resolved ianmspencer

    (@ianmspencer)


    This seems to be common across any WordPress system using the rich text editor. I’ve found some supposed fixes but they don’t work.

    Simple problem. I have a front end post form to create a vanilla WordPress post. I insert a picture. I save, it shows correctly. I edit the post using the front end, the pictures are not there. Checking the picture, the link has been quoted.

    So this is my correctly formatted post created using the form first time through – all good:

    This is what I see if I then select the post through the WP User Front end and edit it:

    And clicking on the broken photo placeholders:

    So simply reopening the post breaks the formatting.

    If I go into the backend editor I see this:

    So it seems that the Rich Text Editor is incompatible with WordPress 6.6.1

    Having Googled I’ve tried blocking the editor processing with:

    // Add a hook.
    add_filter( 'run_wptexturize', '__return_false', 10 );

    using WPCode to insert but that does not seem to help.

    What to do?

    WordPress 6.6.1

    Theme Fork Version: 1.0.8

    WP User Frontend Version 4.0.11

    However, this happens on Pixelite Events Manager too, it is a problem with the editor.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Saiful Islam

    (@saifislam01)

    Hi @ianmspencer,

    Thank you for reaching out!

    It sounds like you’re experiencing an issue where images are missing after editing a post via the WP User Frontend plugin’s front-end post form. This may happen if the image links are being encoded or quoted incorrectly during the editing process.

    Here are a few steps you can take to troubleshoot and resolve this issue:

    1. Ensure that the users editing the post have the correct permissions to upload media files. Sometimes, restricted media permissions may cause images to disappear or break during editing.
    2. The WP User Frontend plugin might be automatically encoding certain HTML entities, causing image URLs to be quoted incorrectly. You can test this by checking the form’s HTML processing settings and disabling any auto-encoding features.
    3. Double-check the configuration for the image upload field in the post form. Ensure that it is properly set to allow editing and that the field is not restricted or overwritten when the post is edited.
    4. Sometimes, conflicts with other plugins can interfere with the way WP User Frontend handles media or post content. Try deactivating other plugins temporarily to see if the issue persists.

    If none of these steps resolve the issue, it would be helpful to know the following:

    • What exact format is the image URL being quoted as?
    • Are you using any custom code to modify post content?

    Feel free to reach out with this information, and I’ll be happy to assist further.

    Best regards,

    Thread Starter ianmspencer

    (@ianmspencer)

    Thank you for the detailed reply.

    I am confident that the issue is that the WP User Front End form is using the old block editor and there is an incompatibility with this and the block themes. Hence I can use the “classic block” in the Admin view of the post but using the front end (with administrator authority) is forcing some pre-processing on links causing the link quotes to be quoted, breaking the code.

    There is apparently no option on the form to switch off pre-processing.

    This also affects the More except tag which gets processed into text.

    As I mentioned, I attempted to switch off pre-processing using the run_wptexturize filter using the WP_Code method of injecting the code into the site, but this did not work even though WP_Code suggested the code was active on the page.

    I suspect the solution is that the form needs to use the classic block when in a Gutenberg theme.

    Plugin Support Saiful Islam

    (@saifislam01)

    Hi @ianmspencer,
    You’re most welcome.

    It seems you’re encountering an issue with WP User Frontend forms and block themes. The problem likely stems from an incompatibility between the classic editor used by WP User Frontend and your theme’s block editor. WP User Frontend does not offer a built-in option to disable pre-processing, which is affecting how links and tags like “More except” are handled on the frontend.

    Alternatively, consider temporarily switching to a classic theme to confirm if the block-editor compatibility is the root cause.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.