View Issue Details

IDProjectCategoryView StatusLast Update
0007968OXID eShop (all versions)2.2. Shop settingspublic2026-07-01 09:02
ReporterSleTp Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
Product Version7.5.0 
Summary0007968: The assignment windows do not display any data anymore
DescriptionWith "assignment window" i mean the small windows that open after you click something like the "assign countries to a payment method" or "assign categories to a product" buttons.
After we updated to Oxid metapackage-ee version 7.5 these assignment windows stop displaying any data.

This seems to happen because the the Core/Config.php has been adjusted so that in the getConfigParam() does not call "init()" anymore. Instead it only calls "initVars()". This makes it so that the session does not get properly initialized in the source/oxajax.php anymore. For now we fixed it ourselves by directly calling Config->init() in oxajax.php.
Steps To Reproduce- Go into the admin backend of an OXID 7.5 instance
- Goto shop config > payment methods
- Select any payment method
- Go into the countries tab
- Click on the assign countries button
- The window now opens, you see the two assignment columns but they are empty
TagsAdmin, AJAX
ThemeNot defined
BrowserNot defined
PHP Version8.4
Database VersionNot defined

Activities

SvenBrunk

2026-07-01 08:40

administrator   ~0018567

I can not reproduce this. I admit my current 7.5 development environment is not completely clean, but the list fills fine.
@SleTp maybe some module is intervening here?

SleTp

2026-07-01 08:56

reporter   ~0018568

@SvrenBrunk - i do not think that any module is intervening. The problem occures quite early in the oxajax.php, since the session can not be initialized and it thinks that the user is not logged in:

    // authorization
    if (
        !(
            Registry::getSession()->checkSessionChallenge() &&
            count(Registry::getUtilsServer()->getOxCookie()) &&
            Registry::getUtils()->checkAccessRights()
        )
    ) {
        header("location:index.php");
        Registry::getUtils()->showMessageAndExit("");
    }

After debugging the issue myself i could not determine where the oxajax.php initializes the session since Core/Config.php has been changed to not do that anymore:

    public function getConfigParam($name, $default = null)
    {
        $this->initVars($this->getShopId()); // <=== This previously was a call to "init()" which initialized the session in oxajax.php, even if incidentally

        if (isset($this->_aConfigParams[$name])) {
            $value = $this->_aConfigParams[$name];
        } elseif (isset($this->$name)) {
            $value = $this->$name;
        } else {
            $value = $default;
        }

        return $value;
    }

Would it be possible to gain access to a test OXID admin backend that is mostly empty to verify that the issue is really unique to us?