BuddyDev

Search

How can I best achieve my perfect single photo view?

Tagged: ,

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 16, 2025 at 12:02 am #55523

    Line 183 of shortcode-gallery-list.php has a crash bringing typo – 'class' => 'mpp-gallery',

    In the original file, the end comma is a full stop.

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 16, 2025 at 2:25 am #55524

    That was my bad, it turns out.

    Things are going from bad to worse. I now have a situation where the js fails only on the MPP settings page. But, the failures seem to be due to WordPress deciding that all & symbols on the page need to be swapped to & currently this in only happening on the MPP settings page, but I had to deactivate a news-ticker plugin that was doing the same thing.

    I’m not stressing, though, the front end is still working as it was. It is missing the zoom, but, it’s loading the wrong image and there is nothing to zoom.

    I did deactivate all plugins, and nothing changed..

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 16, 2025 at 2:27 am #55525

    & symbols are being swapped for & # 0 3 8; – remove the spaces, your wordpress refuses to print those when placed together. It seems related to checking for block based content in wptexturise.

    • This reply was modified 3 days, 10 hours ago by Venutius.
  • Keymaster
    (BuddyDev Team)
    Posts: 25006
    Brajesh Singh on June 16, 2025 at 2:37 am #55527

    Hi George,
    You have some esc_html or similar escape on the page and that seems to be causing it.
    My suggestion is to disable customizations temporarily.

    If you believe this is the default behaviour, Please link me to page structure and MediaPress version(1.x or 2.x you are using) and I will quickly update.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 16, 2025 at 8:11 pm #55531

    Yes, this is not Mediapress, Mediapress is affected because the js for the settings reveal is looking for an & in the link string, and can’t find it. but the same thing seems to be happening to all the backend pages. I’ll wait till later tonight and do another plugin deactivation session. It has to be a plugin somewhere.

  • Keymaster
    (BuddyDev Team)
    Posts: 25006
    Brajesh Singh on June 17, 2025 at 6:55 am #55532

    Hi George,
    Thank you for confirming that it is not MediaPress.

    Please do let me know when you find the culprit.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 17, 2025 at 8:12 am #55535

    I renamed the plugins directory and selected the 2021 theme and it is still happening.

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 17, 2025 at 9:35 am #55536

    Ok, learning every day 🙂

    It seems that having an ampersand printed as # 0038 ; is expected behaviour, and that it is some js, that is not recognising that expected expression that is failing. it is an html decode issue.

  • Keymaster
    (BuddyDev Team)
    Posts: 25006
    Brajesh Singh on June 17, 2025 at 9:40 am #55537

    Hi George,
    You are right. It is encoded entity code for the ampersand(&). The value should be &#38.

    I lack context about the issue/js, so unable to comment further.

    Regards
    Brajesh

  • Participant
    Level: Master
    Posts: 459
    Venutius on June 17, 2025 at 11:24 am #55539

    On the MediaPress settings page, the contnt loads, but then then all tabs are hidden, and I get the following error:

    [2025-06-17 11:20:37] - Javascript Message: Uncaught Error: Syntax error, unrecognized expression: #038; - URL: https://brigantesnation.com/wp-admin/load-scripts.php?c=0&loadchunk_0=jquery-core,jquery-migrate,utils,wp-hooks,jquery-ui-core,underscore,moxiejs,plupload,jquery-ui-mouse,jquery-ui-sortable,jquery-t&loadchunk_1=ouch-punch&ver=c6d0b1135633ba322c1db55348037e4b - Line: 2

    I thought it was because the ampersand was being misprinted, but now I understand that this printed behaviour is correct, and that some js on this page is failing to recognise that content.

You must be logged in to reply to this topic.

This topic is: not resolved