BoldMinded

All add-ons currently require PHP 7.4 or greater.

On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.

Publisher does not support the Fluid field type. Please do not contact asking when support will be available.

If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.

Ticket: After changing language with publisher add-On, parameters appear on URL

Status Resolved
Add-on / Version Speedy 1.7.0
Severity
EE Version 6.4.6

Cleiton da Silva

Dec 11, 2023

Hello,

I’m experiencing an issue with the Speedy and Publisher add-ons on a website that supports three different languages. For reference, I am currently using the following code to obtain the languages along with links for changing:
{exp:publisher:languages}

  • {long_name}

    • {/exp:publisher:languages}

    The problem is that after changing to a different language, the Publisher add-on adds parameters after the normal URL with the language (ex: test.com/en or test.com/es)
    turning into something like this:
    test.com/en?&&a=JJJ47QQQ&action=JJJ1QQQ&ajax=JJJ32QQQ&c=JJJ15QQQ&charset=JJJ24QQQ&code=JJJ10QQQ&comment=JJJ30QQQ&content=JJJ29QQQ&continue=JJJ70QQQ&dZFaK=JJJ75QQQ&data=JJJ16QQQ&debug=JJJ33QQQ&dest=JJJ68QQQ&dir=JJJ56QQQ&do=JJJ49QQQ&edit=JJJ42QQQ&email=JJJ6QQQ&error=JJJ36QQQ&f=JJJ4QQQ&file=JJJ8QQQ&filename=JJJ60QQQ&filter=1%20waitfor%20delay%20%270:0:15%27%20—%20&format=JJJ39QQQ&from=JJJ45QQQ&group=JJJ63QQQ&h=JJJ58QQQ&id=JJJ0QQQ&key=JJJ21QQQ&lang=JJJ19QQQ&limit=JJJ48QQQ&login=JJJ27QQQ&m=JJJ66QQQ&mode=JJJ17QQQ&name=JJJ3QQQ&next=JJJ72QQQ&offset=JJJ41QQQ&order=JJJ18QQQ&p=JJJ20QQQ&page=JJJ2QQQ&pass=JJJ55QQQ&path=JJJ54QQQ&plugin=JJJ50QQQ&post=JJJ26QQQ&preview=JJJ43QQQ&q=JJJ11QQQ&query=JJJ35QQQ&redirect=JJJ61QQQ&reference=JJJ73QQQ&s=JJJ25QQQ&save=JJJ37QQQ&search=JJJ28QQQ&show=JJJ57QQQ&site=JJJ74QQQ&sort=JJJ38QQQ&start=JJJ23QQQ&state=JJJ34QQQ&status=JJJ22QQQ&step=JJJ31QQQ&subject=JJJ65QQQ&t=JJJ14QQQ&tab=JJJ40QQQ&template=JJJ64QQQ&test=JJJ53QQQ&text=0%27XOR(if(now()=sysdate()%2Csleep(15)%2C0))XOR%27Z&theme=JJJ51QQQ&title=JJJ9QQQ&token=JJJ13QQQ&type=JJJ7QQQ&u=JJJ67QQQ&uri=JJJ69QQQ&url=JJJ5QQQ&user=JJJ12QQQ&value=JJJ59QQQ&view=%27

    The thing is, when I clear the Speedy cache, the URLs come back to normal without the parameters, and after a while (few minutes), they come back again.

    Can you help me figure out what’s going on?

    #1

    BoldMinded (Brian)

    I don’t think has anything to do with Publisher or Speedy actually. If it works fine without Speedy, and this is fixed when you clear the cache, then something is creating the cache with those URLs, and none of those query parameter names, “ajax”, “charset” etc are related to Publisher or Speedy. Something is hitting those URLs and creating those cached items.

    #2

    BoldMinded (Brian)

    That almost looks like you’re getting spammed by bots. You’ll have to figure out how to identify and block them.

    #3

    Cleiton da Silva

    Thank you for the quick reply! It makes sense. I’ll make sure to look into it.

    Login to reply