Hi Alexander,
there are some known issues, that will prevent the oxid shop or the oxid
console from fixing some module configuration problems (e.g.
https://github.com/OXID-eSales/oxideshop_ce/pull/333/files),
but if you have delete the module, deleted the database config and cleared the
cache i
Hello André,
yes, here is the workflow:
logout from the shop(clear cookies, cache).
delete all module entrties from database oxconfig table.
clear /tmp folder
Login into the shop, go to Extensions -> Modules, still have those entries in
modules overview.
Yes it’s really weird, i never had such a
Hi ALexander,
did you clear tmp after removing module entries of oxconfig?
Just to be sure. Otherwise this is really weird :-D
Best
André
Am Mittwoch, 30. März 2016, 11:47:00 schrieb Alexander Scheider:
> Hello André,
>
> no it’s not production system.
> After execution of your statement i s
Hello Frank,
i cleared /tmp folder after removing modules from oxconfig.
I also cleared all browser cache and cookies.
The entries are still there.
Kind regards,
Alexander Scheider
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Fran
Hi Alexander,
Module config is also cached in /tmp
Greets,
Frank
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander
Scheider
Gesendet: Mittwoch, 30. März 2016 13:21
An: dev-general@lists.oxidforge.org
Betreff: Re: [
Hello André,
no it’s not production system.
After execution of your statement i still have those classes in all module
extends.
Here example export of trosofortueberweisung:
"_OXID_ESHOP_MODULES_CONFIGURATION_": {
"sShopVersion": "5.2.7",
"sShopEdition": "EE",
"sShopId": 1
Hi Alexander,
in case its not a productive system and you just want to get rid of these
module
entries, you can simply do that via database (Backup of oxconfig recommended
;-) ).
DELETE FROM oxconfig WHERE OXVARNAME LIKE '%module%'
After performing this query all Modules in all subshops shoul
Hello Alexander,
thank you for your answer.
the ffb/metadata.php file does not exists anymore. It is old module which is
was removed on shop update.
The old module had no invalid entries and worked pretty well with OXID EE 4.6.3
The metadata of old module contains classes which can't be removed:
Hi Alexander,
did you check the ffb/metadata.php for invalid entries? There could be
an old/invalid entry, maybe you reference a file there that does no
longer exists?
If you are using PHPStorm with the OXID Plugin enabled, you will have
syntax support for metadata.php!
Best regards
--
Al
Hi folks,
I'm using OXID EE 5.2.7 and have a problem with old module entries which can't
be deleted in OXID backend or database.
Every time by clicking on Extensions -> Modules i get following list:
[cid:image002.jpg@01D18A84.823395F0]
After click on yes i see the list with all installed modul
10 matches
Mail list logo
