Undefined <feature>work upon upgrade to new version

[pma-import]

This report is related to user submitted report #11887 on the phpmyadmin error reporting server.

---

• Original URL: https://sourceforge.net/p/phpmyadmin/bugs/4984/
• Original author: phpmyadmin-bot
• Found in version: 4.4.11

[pma-import]

For extra features offered by phpMyAdmin, work parameters are used to check whether each feature is active. These are defined at https://github.com/phpmyadmin/phpmyadmin/blob/RELEASE_4_4_11/libraries/relation.lib.php#L421-L438.
PMA_getRelationsParam() returns these values cached in the session and these values will not go undefined unless in a version upgrade. Caching is essential IMO and my suggestion is to mark this ticket as wont-fix requiring the user to re-login upon upgrade.

---

• Original author: madhuracj

[pma-import]

Madhura,
do you think that a version upgrade explains all occurrences of this incident?

---

• Original author: lem9

[pma-import]

I see two patterns in accessing these variables
$cfgRelation = PMA_getRelationsParam(); $cfgRelation['menuswork']
or
$GLOBALS['cfgRelation']['menuswork']

Value for $GLOBALS['cfgRelation'] is set inside PMA_getRelationsParam(). So I do not see any other way of some work variable being not set, other than in a version upgrade

---

• Original author: madhuracj

[pma-import]

Makes sense, so marking as "won't fix" also makes sense (unless someone starts to add isset() verifications everywhere).

---

• Original author: lem9

[pma-import]

I think it's better to put this in docs. #1791

---

• Original author: madhuracj

[pma-import]

I think adding isset() verification does not make sense as these variables are always defined except in an upgrade. In fact, these variables can be used to avoid isset() check for other pmadb variables. For example:
if ($cfgRelation['menuswork']) { $groupTable = PMA_Util::backquote($cfgRelation['usergroups']); }

---

• Original author: madhuracj

[pma-import]

Let's hope users will read the doc :) because we have a ton of these error reports.

---

• Original author: lem9

[pma-import]

How about storing version number in the session and if that differs from current one force logout?

---

• Original author: nijel

[pma-import]

That would work (except with the 'config' auth).

---

• Original author: lem9

[madhuracj]

Fixed with 1599481