Re: [oxid-dev-general] OXID EE2.7 Firefox 3.5 Drag'n'Drop Bug solved [Vorgang: #997II9PJV5]
Hi Vilma, oh, sorry about that.. I thought this was a general OXID DEV mailing list (I guess the name oxid-dev-general is a bit misleading if somebody didn't read the instructions on OxidForge ...). Nevermind then :) And the answer in German wasn't intended, I didn't realize that hitting reply goes straight back to the whole list when I answered to Martina. Sorry again cheers, Stefan Vilma Liorensaityte schrieb: Hi, Thank you Stefan for the patch to EE, but this list is about CE only. You can discuss the EE 2.7 patch in the forum, but not on dev-general, because we want to keep dev-general a list for developers of the open source licensed version. And I must remind you, this is an English only list! Should there be any other questions about usage of this mailing list, please consult http://www.oxidforge.org/wiki/Mailinglists and feel free to ask questions to this list. Cheers, Vilma Von: dev-general-boun...@lists.oxidforge.org im Auftrag von Stefan Moises Gesendet: Pn 2009.07.24 10:32 An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] OXID EE2.7 Firefox 3.5 Drag'n'Drop Bug solved [Vorgang: #997II9PJV5] hey, Du bist doch im Urlaub! ;) i...@bastelundhobbykiste.de schrieb: ach du bist stefam :) cool !! Bitte beachten Sie, dass urlaubsbedingt vom 25. Juli bis zum 23. August 2009 KEINE LIEFERUNGEN stattfinden Mit freundlichen Grüßen Martina Schimbach http://FollowMeButton.com/auth.php?user=laramarco Martinas Bastel- Hobbykiste Kundenbetreuung Bestellhotline: 0800-9655324 Martinas Bastel- Hobbykiste Inh. Martina Schimbach Zum Grund 9 35796 Blessenbach Germany USt-IdNr.: DE 187589656 Tel: 0049 (0) 6474 - 882816 Fax: 0049 (0) 6474 - 8525 Internet: http://www.bastelundhobbykiste.de http://www.bastelundhobbykiste.de/ oder http://www.kreative-buecher.de http://www.kreative-buecher.de/ e-Mail: i...@bastelundhobbykiste.de -Ursprüngliche Nachricht- Gesendet: 24.07.2009 10:24:39 Von: Stefan Moises moi...@shoptimax.de An: dev-general@lists.oxidforge.org Betreff: [oxid-dev-general] OXID EE2.7 Firefox 3.5 Drag'n'Drop Bug solved Vorgang: 997II9PJV5 Hi all, in OXID EE 2.7 the drag and drop functionality in the shop admin doesn't work anymore because of a problem with the old rico.js lib OXID uses. Here is the fix: http://www.oxid-esales.com/forum/showthread.php?p=11201#post11201 Cheers, Stefan -- *** Stefan Moises Senior Softwareentwickler shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-25 Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de http://www.shoptimax.de/ *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- *** Stefan Moises Senior Softwareentwickler shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-25 Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de http://www.shoptimax.de/ *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- *** Stefan Moises Senior Softwareentwickler shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-25 Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
[oxid-dev-general] Proposal: use spl_autoload_register() instead of __autoload() to allow other autoload functions in OXID
Hi List,
I'd like to make a proposal:
OXID defines its own __autoload() function in core/oxfunctions.php,
which makes it hard to add external libraries containing their own
autoloaders or to implement different autoloaders for own classes/libs.
A solution would be to rename that function to e.g. oxidAutoload() and
to add it to the PHP autoloader stack with
*spl_autoload_register('**oxidAutoload');*
So other autoload functions could be added in the same way, too.
What do you think?
Cheers,
Stefan Moises
--
***
Stefan Moises
Senior Softwareentwickler
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Tel.: 0911/25566-25
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] Beta of OXID eShop version 4.5.0 Coming Before Christmas
Yes, and what about third party modules? AFAIK there was no info posted so far even for the OXID partners... shouldn't they also know how to work with this new module installation feature? Cheers, Steafn Am 01.12.2010 14:26, schrieb Alexander Kludt: Yes big news, personally I'm interested in the module installer - especially when it comes to changed_full structure import, can you already give some information on the new system? Ashant Chalasani schrieb: This is great news! I wish a bit of info about Template Inheritance was posted, but never mind, I'll post about it at http://goo.gl/BNuqJ Happy hoxlidays with 4.5! Ashant __ http://www.euroblaze.de 2010/12/1 Marco Steinhaeuser marco.steinhaeu...@oxid-esales.com mailto:marco.steinhaeu...@oxid-esales.com Hi everybody, today, we published a new blog post: A beta version of OXID eShop 4.5.0 will still come before Christmas. Besides a newly designed store front, it will contain some interesting enhancements to the Smarty Template Engine (inheritance) and a module and template installer. Read more: http://www.oxid-esales.com/en/news/blog/announcing-oxid-eshop-version-450-beta Regards Marco ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- *** Stefan Moises Senior Softwareentwickler shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-25 Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] [oxid-dev-general] Shop config access from template
Hi,
good point, I was wondering that myself... such a function would be
really helpful, and since oxViewConfig can be extended by a module,
you can easily make an oxViewConf module and add this function, so you
can use [{ $oViewConf-getConfigParam('someValue') }] in your templates:
class myOxViewConfig extends myOxViewConfig_parent
{
public function getConfigParam( *$sParamName* )
{
return $this-getConfig()-getConfigParam( *$sParamName* );
}
}
And in Admin add this to the Modules section:
oxviewconfig = myoxviewconfig
Cheers,
Stefan
Am 17.02.2011 14:15, schrieb GiedriusK:
Hi,
How to access shop config parameters from Smarty template?
I noticed many functions in *oxviewconfig.php* like:
/**
* Returns facebook application key value
*
* @return string
*/
public function getFbAppId()
{
return $this-getConfig()-getConfigParam( 'sFbAppId' );
}
What is the reason not to have smth like this?:
public function getConfigParam( *$sParamName* )
{
return $this-getConfig()-getConfigParam( *$sParamName* );
}
Thank You for advice.
giedr...@nfq.lt mailto:giedr...@nfq.lt
--
***
Stefan Moises
Senior Softwareentwickler
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Tel.: 0911/25566-25
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
[oxid-dev-general] new module structure in 4.6 and admin include files not working?
Hi list,
I am trying to port a module to the new Oxid 4.6. module logic and
having a hard time getting the paths etc. right... now I seem to have
hit the wall with admin includes:
[11-May-2012 15:07:06] PHP Warning: include_once(): Failed opening
'inc/smxb2b_accounts_main.inc.php' for inclusion
(include_path='.:/usr/local/lib/php') in
/...smxDemoshopB2B46/admin/oxajax.php on line 740
The file smxb2b_accounts_main.inc.php is located at
/modules/shoptimax/smxb2b_accounts/admin/inc/ and included from
/modules/shoptimax/smxb2b_accounts/admin/smxb2b_accounts_main.php. At
first, not even that was working and I had to adjust the path to the
include in my admin class. Now that part is working, but oxajax can't
find the include now as you can see...
I've tried to set the include path with PHP like this:
if (oxConfig::getParameter(aoc))
{
$newIncPath = dirname(__FILE__);
set_include_path(get_include_path() . PATH_SEPARATOR .
$newIncPath);
$aColumns = array();
include_once 'inc/' . strtolower(__CLASS__) . '.inc.php';
$this-_aViewData['oxajax'] = $aColumns;
return popups/ . $this-_sThisTemplate;
}
This works for my admin class, but not for oxajax.php...
I also can't set the path for this include file in my metadata.php,
because it isn't a real class like the main admin class:
'files' = array(
'smxb2b_accounts_main'=
'shoptimax/smxb2b_accounts/admin/smxb2b_accounts_main.php',
'ajaxComponent' =
'shoptimax/smxb2b_accounts/admin/inc/smxb2b_accounts_main.inc.php',
...
I've tried to set the path for ajaxComponent as you can see, but of
course this isn't working either...
So is there any way I can get oxajax to load my include file from the
modules directory, or do I have to copy it over to the /admin/inc/ dir
of the shop (which would break the whole concept :P)
And another path question: is there a way to load the
bottomnavicustom.tpl from my module folder, too? E.g. this doesnt
seem to overwrite the default template:
'templates' = array(
bottomnavicustom.tpl=
shoptimax/smxb2b_accounts/out/admin/tpl/bottomnavicustom.tpl,
smxb2b_accounts.tpl =
shoptimax/smxb2b_accounts/out/admin/tpl/smxb2b_accounts.tpl,
...
My own template is found, but bottomnavi is not overwritten with my
version
Thanks a lot,
Stefan
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
***
Stefan Moises
Senior Softwareentwickler
Leiter Modulentwicklung
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] new module structure in 4.6 and admin include files not working?
submitted as bug now at https://bugs.oxid-esales.com/view.php?id=4037
Best,
Stefan
Am 14.05.2012 09:56, schrieb Stefan Moises:
any idea from the OXID developers? :)
Thanks,
Stefan
Am 11.05.2012 15:20, schrieb Stefan Moises:
Hi list,
I am trying to port a module to the new Oxid 4.6. module logic and
having a hard time getting the paths etc. right... now I seem to have
hit the wall with admin includes:
[11-May-2012 15:07:06] PHP Warning: include_once(): Failed opening
'inc/smxb2b_accounts_main.inc.php' for inclusion
(include_path='.:/usr/local/lib/php') in
/...smxDemoshopB2B46/admin/oxajax.php on line 740
The file smxb2b_accounts_main.inc.php is located at
/modules/shoptimax/smxb2b_accounts/admin/inc/ and included from
/modules/shoptimax/smxb2b_accounts/admin/smxb2b_accounts_main.php.
At first, not even that was working and I had to adjust the path to
the include in my admin class. Now that part is working, but oxajax
can't find the include now as you can see...
I've tried to set the include path with PHP like this:
if (oxConfig::getParameter(aoc))
{
$newIncPath = dirname(__FILE__);
set_include_path(get_include_path() . PATH_SEPARATOR .
$newIncPath);
$aColumns = array();
include_once 'inc/' . strtolower(__CLASS__) . '.inc.php';
$this-_aViewData['oxajax'] = $aColumns;
return popups/ . $this-_sThisTemplate;
}
This works for my admin class, but not for oxajax.php...
I also can't set the path for this include file in my metadata.php,
because it isn't a real class like the main admin class:
'files' = array(
'smxb2b_accounts_main'=
'shoptimax/smxb2b_accounts/admin/smxb2b_accounts_main.php',
'ajaxComponent' =
'shoptimax/smxb2b_accounts/admin/inc/smxb2b_accounts_main.inc.php',
...
I've tried to set the path for ajaxComponent as you can see, but of
course this isn't working either...
So is there any way I can get oxajax to load my include file from the
modules directory, or do I have to copy it over to the /admin/inc/
dir of the shop (which would break the whole concept :P)
And another path question: is there a way to load the
bottomnavicustom.tpl from my module folder, too? E.g. this doesnt
seem to overwrite the default template:
'templates' = array(
bottomnavicustom.tpl=
shoptimax/smxb2b_accounts/out/admin/tpl/bottomnavicustom.tpl,
smxb2b_accounts.tpl =
shoptimax/smxb2b_accounts/out/admin/tpl/smxb2b_accounts.tpl,
...
My own template is found, but bottomnavi is not overwritten with my
version
Thanks a lot,
Stefan
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
***
Stefan Moises
Senior Softwareentwickler
Leiter Modulentwicklung
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] new module structure in 4.6 and admin include files not working?
Hello Björn,
thanks a lot, good idea to use functions.php and oxutilsView to load the
admin includes even in oxajax.php and the overwritten templates from the
module directory!
Now I have everything loaded and packed nice and clean in my module dir,
no need to copy anything into the core shop dirs anymore... sweet :)
If anybody else is using admin/inc/...inc.php file includes in custom
modules, just add this to your functions.php file:
# add module admin dirs to include path to get the admin/inc/*.inc.php
files working!
$aModuleDirs = glob( dirname(__FILE__) . '/*/admin/', GLOB_ONLYDIR);
$aModuleDirsVendor = glob( dirname(__FILE__) . '/*/*/admin/', GLOB_ONLYDIR);
$aIncludeDirs = array_merge( $aModuleDirs, $aModuleDirsVendor );
if (is_array($aIncludeDirs) count($aIncludeDirs)) {
foreach($aIncludeDirs as $sIncDir) {
set_include_path(get_include_path() . PATH_SEPARATOR . $sIncDir);
}
}
And for overwriting templates, create an oxutilsview module like so (of
course, adjust name and paths used):
class smxb2b_oxutilsview extends smxb2b_oxutilsview_parent
{
/**
* Initializes and returns templates directory info array
*
* @return array
*/
public function getTemplateDirs()
{
$myConfig = $this-getConfig();
if ( !$this-isAdmin() ) {
$this-setTemplateDir( $myConfig-getModulesDir( true ) .
shoptimax/smxb2b_accounts/out/.$myConfig-getConfigParam( 'sTheme'
)./tpl/ );
}
else {
$this-setTemplateDir( $myConfig-getModulesDir( true ) .
shoptimax/smxb2b_accounts/out/admin/tpl/ );
}
return parent::getTemplateDirs();
}
}
I guess I will write a little blog entry this week about all the little
pitfalls when updating modules to Oxid 4.6...
Cheers,
Stefan
Am 14.05.2012 11:52, schrieb WBL Björn Lange:
Hello Stefan,
Am 11.05.2012 15:20, schrieb Stefan Moises:
This works for my admin class, but not for oxajax.php...
I also can't set the path for this include file in my metadata.php,
because it isn't a real class like the main admin class:
'files' = array(
'smxb2b_accounts_main'=
'shoptimax/smxb2b_accounts/admin/smxb2b_accounts_main.php',
'ajaxComponent' =
'shoptimax/smxb2b_accounts/admin/inc/smxb2b_accounts_main.inc.php',
...
I've tried to set the path for ajaxComponent as you can see, but of
course this isn't working either...
So is there any way I can get oxajax to load my include file from the
modules directory, or do I have to copy it over to the /admin/inc/
dir of the shop (which would break the whole concept :P)
The admin/inc/-Container is identified by the container-parameter.
The oxajax.php script is called directly and not through the
shopcontrol, but the modules/functions.php is included. So you can set
your include-path in this modules/functions.php to resolve
include_once 'inc/'.$sContainer.'.inc.php'; in oxajax.php on 748
(OXID 4.6.0). Did you try this allready?
And another path question: is there a way to load the
bottomnavicustom.tpl from my module folder, too? E.g. this doesnt
seem to overwrite the default template:
'templates' = array(
bottomnavicustom.tpl=
shoptimax/smxb2b_accounts/out/admin/tpl/bottomnavicustom.tpl,
smxb2b_accounts.tpl =
shoptimax/smxb2b_accounts/out/admin/tpl/smxb2b_accounts.tpl,
The Module-Templates are saved in the config var aModuleTemplates
which are called in oxconfig::getTemplatePath after the standard logic:
public function getTemplatePath( $sFile, $blAdmin )
{
$sTemplatePath = $this-getDir( $sFile, $this-_sTemplateDir,
$blAdmin );
if (!$sTemplatePath) {
$sBasePath= getShopBasePath();
$aModuleTemplates =
$this-getConfigParam('aModuleTemplates');
So there is no way to override a default template with this way. But
i suggest to overload oxUtilsView::getTemplateDirs to add your own
template dir first for overwriting this template and load your
template first.
Regards,
Björn
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
***
Stefan Moises
Senior Softwareentwickler
Leiter Modulentwicklung
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] Metadata: Problems on registering multiple entries for one class
Hi OXID devs, any news on this? We have a problem now updating the latest modules to OXID 4.6.x because of multiple inheritance reasons we need to do something like this in the metadata.php (which doesn't work): 'extend' = array( 'search'= 'shoptimax/shoptifind/shoptifind_view_base', 'search'= 'shoptimax/shoptifind/shoptifind_search', ... This doesn't work either: 'extend' = array( 'search'= 'shoptimax/shoptifind/shoptifind_view_baseshoptimax/shoptifind/shoptifind_search', ... Background: to avoid code duplication we need a common base class for different views (but can't extend from it because of the extends xy_parent logic in OXID... and as you know PHP doesn't support multiple inheritance unfortunately (and don't tell me to use PHP 5.4's traits instead :P) Thanks, Stefan Am 29.06.2012 17:02, schrieb Rimvydas Paskevicius: Hi all, Its nice to see discussing about modules handling, so after some internal discussion we decided to add multiple modules entries for one class support in one of the next releases. Hope this will make life easier for modules writers. Rimvydas rimvydas.paskevic...@oxid-esales.com mailto:rimvydas.paskevic...@oxid-esales.com Phone +370 37 333053 Fax +370 37 333054 www.oxid-esales.com http://www.oxid-esales.com ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Tel.: 0911/25566-0 Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] Metadata: Problems on registering multipleentries for one class [T-P86G0139EG-98]
Hi, thanks, this seems to kinda work and the modules are loaded! But for some strange reason, if I do this, the module is always displayed as inactive (although it IS "active" and working)... and there is always the "Activate" button, so there is no change to de-activate it any more :P But at least the module seems to be working now... So, OXID-Devs, you only have to fix the activation if arrays are used in the "extend" section :) Thanks, Stefan Am 16.08.2012 15:55, schrieb Kundenservice | digidesk - media solutions: Hey, just try it with an array, thisworks ( at least its displayed correct in the admin-section ): 'extend' = array( 'search' = array( 'shoptimax/shoptifind/shoptifind_view_base', 'shoptimax/shoptifind/shoptifind_search' ), Mit freundlichen Gren aus Verl Patrick Nussbaum Technik - - digidesk media solutions Inh. Marco Mller Kapellenweg 76 D-33415 Verl - Telefon: +4952469099110 Telefax: +4952469099120 E-Mail: tech...@digidesk.de Web: www.digidesk.de -Ursprngliche Daten- Datum: 16.08.2012 15:48:21 Von: Stefan Moises moi...@shoptimax.de An: dev-general@lists.oxidforge.org Betreff: Re: [oxid-dev-general] Metadata: Problems on registering multipleentries for one class Vorgang: T-P86G0139EG-98 Hi OXID devs, any news on this? We have a problem now updating the latest modules to OXID 4.6.x because of "multiple" inheritance reasons we need to do something like this in the metadata.php (which doesn't work): 'extend' = array( 'search' = 'shoptimax/shoptifind/shoptifind_view_base', 'search' = 'shoptimax/shoptifind/shoptifind_search', ... This doesn't work either: 'extend' = array( 'search' = 'shoptimax/shoptifind/shoptifind_view_baseshoptimax/shoptifind/shoptifind_search', ... Background: to avoid code duplication we need a common base class for different views (but can't extend from it because of the "extends xy_parent" logic in OXID... and as you know PHP doesn't support multiple inheritance unfortunately (and don't tell me to use PHP 5.4's "traits" instead :P) Thanks, Stefan Am 29.06.2012 17:02, schrieb Rimvydas Paskevicius:
Re: [oxid-dev-general] Metadata: Problems on registering multipleentries for one class [T-P86G0139EG-98]
Hi list,
I have found the problem - oxmodule::isActive() does not
check for module arrays defined in metadata.php, below is a fixed
version... until OXID fixes the bug, you can use this module to
overwrite the oxmodule class so that your module is displayed
correctly as being "active" :)
(added code in BOLD) - you can add this module to
metadata.php like this:
'extend' = array(
// here is a "problematic" entry with two classes in an
array
'search' =
array('shoptimax/shoptifind/shoptifind_view_base',
'shoptimax/shoptifind/shoptifind_search'),
...
'oxmodule'=
'shoptimax/shoptifind/smx_oxmodule',
}
And here is the module code which checks for module arrays for one
extended class, too:
class smx_oxmodule extends smx_oxmodule_parent {
/**
* Check if extension is active
*
* @return bool
*/
public function isActive()
{
$blActive = false;
$sId = $this-getId();
if (isset($sId)) {
if ( is_array($this-_aModule['extend'])
!empty($this-_aModule['extend']) ) {
$aAddModules = $this-_aModule['extend'];
$aInstalledModules = $this-getAllModules();
$iClCount = count($aAddModules);
$iActive = 0;
foreach ($aAddModules as $sClass = $sModule) {
// smx_sm: also check for module arrays
defined for one extended class!
if(is_array($sModule)) {
if(count(array_diff($aInstalledModules[$sClass], $sModule)) == 0)
{
$iActive ++;
}
}
else {
if ( (isset($aInstalledModules[$sClass])
in_array($sModule, $aInstalledModules[$sClass])) ) {
$iActive ++;
}
}
}
$blActive = $iClCount 0 $iActive ==
$iClCount;
$aDisabledModules = $this-getDisabledModules();
if ( $blActive (
is_array($aDisabledModules) in_array($sId,
$aDisabledModules) ) ) {
$blActive = false;
}
} else {
//handling modules that does not extend any class
$aDisabledModules = $this-getDisabledModules();
if ( is_array($aDisabledModules)
!in_array($sId, $aDisabledModules) ) {
$blActive = true;
}
}
}
return $blActive;
}
}
Cheers,
Stefan
Am 16.08.2012 16:05, schrieb Stefan
Moises:
Hi,
thanks, this seems to kinda work and the modules are loaded!
But for some strange reason, if I do this, the module is always
displayed as inactive (although it IS "active" and working)...
and there is always the "Activate" button, so there is no change
to de-activate it any more :P
But at least the module seems to be working now...
So, OXID-Devs, you only have to fix the activation if arrays are
used in the "extend" section :)
Thanks,
Stefan
Am 16.08.2012 15:55, schrieb
Kundenservice | digidesk - media solutions:
Hey,
just try it with an array, thisworks ( at least
its displayed correct in the admin-section ):
'extend' = array(
'search' = array(
'shoptimax/shoptifind/shoptifind_view_base',
'shoptimax/shoptifind/shoptifind_search' ),
Mit freundlichen Gren aus
Verl
Patrick Nussbaum
Technik
-
-
digidesk media solutions
Inh. Marco Mller
Kapellenweg 76
D-33415 Verl
-
Telefon:
+4952469099110
T
Re: [oxid-dev-general] Metadata: Problems on registering multipleentries for one class [T-P86G0139EG-98]
Hi,
yes, no problem with that, looking forward to the full official
multiple inheritance support :)
At least it is already partially supported and you can already use
arrays for the "extend" entries in metadata.php - that's cool ...
But I needed the "full support" now to get our search module
working, so I've extended the functionality in the current OXID
(4.6.3) version... and if anybody else needs it, he can use my
workaround, until this feature is officially supported :)
Cheers,
Stefan
Am 21.08.2012 13:24, schrieb Rimvydas
Paskevicius:
Hi,
Current module handler does not support multiple
inheritance of same class. So what you are using now is hack
and does not officially supported by oxid so it is normal
that something is not working as expected . Some time
ago there was already discussion that there should be
possibility to extend same class more than one time and we
decided that will implement this in one of the next shop
version. So when we will implement this, this feature will
be supported and activation/deactivation will work fine .
Rimvydas
rimvydas.paskevic...@oxid-esales.com
Phone +370 37 333053
Fax +370 37 333054
www.oxid-esales.com
From: Stefan Moises
Sent: Tuesday, August 21, 2012 12:55 PM
To: dev-general@lists.oxidforge.org
Subject: Re: [oxid-dev-general] Metadata:
Problems on registering multipleentries for one class
[T-P86G0139EG-98]
Hi list,
I have found the problem - oxmodule::isActive() does
not check for module arrays defined in metadata.php, below
is a fixed version... until OXID fixes the bug, you can use
this module to overwrite the oxmodule class so that your
module is displayed correctly as being "active" :)
(added code in BOLD) - you can add this module to
metadata.php like this:
'extend' = array(
// here is a "problematic" entry with two classes in
an array
'search' =
array('shoptimax/shoptifind/shoptifind_view_base',
'shoptimax/shoptifind/shoptifind_search'),
...
'oxmodule' =
'shoptimax/shoptifind/smx_oxmodule',
}
And here is the module code which checks for module arrays
for one extended class, too:
class smx_oxmodule extends smx_oxmodule_parent {
/**
* Check if extension is active
*
* @return bool
*/
public function isActive()
{
$blActive = false;
$sId = $this-getId();
if (isset($sId)) {
if ( is_array($this-_aModule['extend'])
!empty($this-_aModule['extend']) ) {
$aAddModules = $this-_aModule['extend'];
$aInstalledModules =
$this-getAllModules();
$iClCount = count($aAddModules);
$iActive = 0;
foreach ($aAddModules as $sClass =
$sModule) {
// smx_sm: also check for module
arrays defined for one extended class!
if(is_array($sModule)) {
if(count(array_diff($aInstalledModules[$sClass],
$sModule)) == 0) {
$iActive ++;
}
}
else {
if (
(isset($aInstalledModules[$sClass])
in_array($sModule, $aInstalledModules[$sClass])) ) {
$iActive ++;
}
}
}
$blActive = $iClCount 0
$iActive == $iClCount;
$aDisabledModules =
$this-getDisabledModules();
if ( $blActive (
is_array($aDisabledModules) in_array($sId,
$aDisabledModules) ) ) {
$blActive = false;
}
} else {
//handling modules that does not extend any
class
$aDisabledModules =
$this-getDisabledModules();
if ( is_array($aDisabledModules)
!in_array($sId, $aDisabledModules) ) {
$blActive = true;
}
}
}
[oxid-dev-general] No installation packages für OXID 4.7.x. / 5.0.x in Oxid Partner SVN anymore?
Dear oxid devs, I know this list is OXID CE-focussed, but I am wondering why there are no installation packages anymore in the Oxid partner SVN? Are we supposed to use the source files of the tagged versions? Will there be encoded, zipped installation packages for PE / EE again in the future? Thanks, best regards, Stefan -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] No installation packages für OXID 4.7.x. / 5.0.x in Oxid Partner SVN anymore?
Hi Björn, ah, thank you.. guess I should start actually reading those newsletters from start to end :) But that leads to another question... does that also mean that we are not forced to encode the PE / EE modules, extensions etc. any more? Was there any official announcement that I've missed, too? Or are we furthermore forced to self-encode the PE/EE sources now, too? Cheers, Stefan Am 12.12.2012 10:03, schrieb Lange, Björn: Hi Stefan, From the Partner-Newsletter: Please be advised that since the last release we do not provide the install packages in the SVN any more. Instead all SOURCE packages (including the packages with the Unit Tests) can be found in the same place as the source code documentation: Regards, Björn ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] No installation packages für OXID 4.7.x. / 5.0.x in Oxid Partner SVN anymore?
One more thing... although the EE / PE shop itself is available as source-only now in SVN, at least the file setup/oxsetup.php is still encoded, obviously for PHP 5.2.? How do we install e.g. OXID EE 5.0.1. on PHP 5.3. if the setup is encoded for 5.2. and there is no source version available? Judging by file size, the file has changed since version 4.6.5., so I'm not sure we can use an older PHP 5.3 encoded setup script... Thanks, Stefan Am 12.12.2012 10:09, schrieb Stefan Moises: Hi Björn, ah, thank you.. guess I should start actually reading those newsletters from start to end :) But that leads to another question... does that also mean that we are not forced to encode the PE / EE modules, extensions etc. any more? Was there any official announcement that I've missed, too? Or are we furthermore forced to self-encode the PE/EE sources now, too? Cheers, Stefan Am 12.12.2012 10:03, schrieb Lange, Björn: Hi Stefan, From the Partner-Newsletter: Please be advised that since the last release we do not provide the install packages in the SVN any more. Instead all SOURCE packages (including the packages with the Unit Tests) can be found in the same place as the source code documentation: Regards, Björn ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] No installation packages für OXID 4.7.x. / 5.0.x in Oxid Partner SVN anymore?
Hi, yeah, it probably will... but it's not a real solution to the problem asking the support for custom-encoded files for every new Oxid version, is it? :) Cheers, Stefan Am 12.12.2012 11:03, schrieb ooxi: Hi, The Support will send you a PHP 5.3 encoded Version, if you ask :) -- ooxi Violetland — An open source cross-platform game similar to Crimsonland — http://violetland.github.com Stefan Moises moi...@shoptimax.de schrieb: One more thing... although the EE / PE shop itself is available as source-only now in SVN, at least the file setup/oxsetup.php is still encoded, obviously for PHP 5.2.? How do we install e.g. OXID EE 5.0.1. on PHP 5.3. if the setup is encoded for 5.2. and there is no source version available? Judging by file size, the file has changed since version 4.6.5., so I'm not sure we can use an older PHP 5.3 encoded setup script... Thanks, Stefan Am 12.12.2012 10:09, schrieb Stefan Moises: Hi Björn, ah, thank you.. guess I should start actually reading those newsletters from start to end :) But that leads to another question... does that also mean that we are not forced to encode the PE / EE modules, extensions etc. any more? Was there any official announcement that I've missed, too? Or are we furthermore forced to self-encode the PE/EE sources now, too? Cheers, Stefan Am 12.12.2012 10:03, schrieb Lange, Björn: Hi Stefan, From the Partner-Newsletter: Please be advised that since the last release we do not provide the install packages in the SVN any more. Instead all SOURCE packages (including the packages with the Unit Tests) can be found in the same place as the source code documentation: Regards, Björn ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Guntherstraße 45 a 90461 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
[oxid-dev-general] OXID Unit-Tests - memory usage?
Hi list,
I am trying to run all the OXID unit tests for the current CE version
using OXVM... although I have raised the used memory from 1024M to
2768M, I still get an out of memory error.. any ideas why? Has anybody
successfully tried to run the current test suite?
Here is the command I am using... my VM has currently 3328MB assigned.
oxPATH=/path/to/oxid/eshop/ oxADMIN_PASSWD='password' phpunit –d
'memory_limit=2768M' --verbose -–bootstrap bootstrap.php AllTestsUnit.php
Call stack is:
...
Unit_Core_oxemailAzureTplTest
...PHP Fatal error: Out of memory (allocated -1998061568) (tried to
allocate 2013009921 bytes) in /usr/share/php/PHPUnit/Util/Type.php on
line 163
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:52
PHP 3. PHPUnit_TextUI_Command-run()
/usr/share/php/PHPUnit/TextUI/Command.php:147
PHP 4. PHPUnit_TextUI_TestRunner-doRun()
/usr/share/php/PHPUnit/TextUI/Command.php:214
PHP 5. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/TextUI/TestRunner.php:350
PHP 6. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:675
PHP 7. PHPUnit_Framework_TestSuite-runTest()
/usr/share/php/PHPUnit/Framework/TestSuite.php:732
PHP 8. OxidTestCase-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:757
PHP 9. PHPUnit_Framework_TestCase-run()
/var/www/eshops/ce473/unittests/unit/OxidTestCase.php:225
PHP 10. PHPUnit_Framework_TestResult-run()
/usr/share/php/PHPUnit/Framework/TestCase.php:653
PHP 11. PHPUnit_Framework_TestCase-runBare()
/usr/share/php/PHPUnit/Framework/TestResult.php:687
PHP 12. PHPUnit_Framework_TestCase-runTest()
/usr/share/php/PHPUnit/Framework/TestCase.php:706
PHP 13. ReflectionMethod-invokeArgs()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 14.
Unit_Core_oxInputValidatorTest-testCheckCountriesGoodCountries()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 15. PHPUnit_Framework_Assert::assertNull()
/var/www/eshops/ce473/unittests/unit/core/oxinputvalidatorTest.php:465
PHP 16. PHPUnit_Framework_Assert::assertThat()
/usr/share/php/PHPUnit/Framework/Assert.php:742
PHP 17. PHPUnit_Framework_Constraint-fail()
/usr/share/php/PHPUnit/Framework/Assert.php:1734
PHP 18. PHPUnit_Framework_Constraint-failureDescription()
/usr/share/php/PHPUnit/Framework/Constraint.php:91
PHP 19. PHPUnit_Util_Type::toString()
/usr/share/php/PHPUnit/Framework/Constraint.php:111
PHP 20. print_r() /usr/share/php/PHPUnit/Util/Type.php:163
No idea why it is only using 2 GB here though
Maybe it's an error trying to send mails which leads to this exception
... because I had to install sendmail since
Unit_Core_oxemailAzureTplTest threw an error in the tests before that it
couldn't find sendmail before the out of memory error occured... now
that error is gone, but out of memory still comes up :(
Thanks,
Stefan
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
***
Stefan Moises
Senior Softwareentwickler
Leiter Modulentwicklung
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] OXID Unit-Tests - memory usage?
Hi,
is nobody using the Unit tests? Are they working for anybody at the moment?
Thanks,
Stefan
Am 08.02.2013 16:25, schrieb Stefan Moises:
Hi list,
I am trying to run all the OXID unit tests for the current CE version
using OXVM... although I have raised the used memory from 1024M to
2768M, I still get an out of memory error.. any ideas why? Has anybody
successfully tried to run the current test suite?
Here is the command I am using... my VM has currently 3328MB assigned.
oxPATH=/path/to/oxid/eshop/ oxADMIN_PASSWD='password' phpunit –d
'memory_limit=2768M' --verbose -–bootstrap bootstrap.php AllTestsUnit.php
Call stack is:
...
Unit_Core_oxemailAzureTplTest
...PHP Fatal error: Out of memory (allocated -1998061568) (tried to
allocate 2013009921 bytes) in /usr/share/php/PHPUnit/Util/Type.php on
line 163
PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:52
PHP 3. PHPUnit_TextUI_Command-run()
/usr/share/php/PHPUnit/TextUI/Command.php:147
PHP 4. PHPUnit_TextUI_TestRunner-doRun()
/usr/share/php/PHPUnit/TextUI/Command.php:214
PHP 5. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/TextUI/TestRunner.php:350
PHP 6. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:675
PHP 7. PHPUnit_Framework_TestSuite-runTest()
/usr/share/php/PHPUnit/Framework/TestSuite.php:732
PHP 8. OxidTestCase-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:757
PHP 9. PHPUnit_Framework_TestCase-run()
/var/www/eshops/ce473/unittests/unit/OxidTestCase.php:225
PHP 10. PHPUnit_Framework_TestResult-run()
/usr/share/php/PHPUnit/Framework/TestCase.php:653
PHP 11. PHPUnit_Framework_TestCase-runBare()
/usr/share/php/PHPUnit/Framework/TestResult.php:687
PHP 12. PHPUnit_Framework_TestCase-runTest()
/usr/share/php/PHPUnit/Framework/TestCase.php:706
PHP 13. ReflectionMethod-invokeArgs()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 14.
Unit_Core_oxInputValidatorTest-testCheckCountriesGoodCountries()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 15. PHPUnit_Framework_Assert::assertNull()
/var/www/eshops/ce473/unittests/unit/core/oxinputvalidatorTest.php:465
PHP 16. PHPUnit_Framework_Assert::assertThat()
/usr/share/php/PHPUnit/Framework/Assert.php:742
PHP 17. PHPUnit_Framework_Constraint-fail()
/usr/share/php/PHPUnit/Framework/Assert.php:1734
PHP 18. PHPUnit_Framework_Constraint-failureDescription()
/usr/share/php/PHPUnit/Framework/Constraint.php:91
PHP 19. PHPUnit_Util_Type::toString()
/usr/share/php/PHPUnit/Framework/Constraint.php:111
PHP 20. print_r() /usr/share/php/PHPUnit/Util/Type.php:163
No idea why it is only using 2 GB here though
Maybe it's an error trying to send mails which leads to this exception
... because I had to install sendmail since
Unit_Core_oxemailAzureTplTest threw an error in the tests before that
it couldn't find sendmail before the out of memory error occured...
now that error is gone, but out of memory still comes up :(
Thanks,
Stefan
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
***
Stefan Moises
Senior Softwareentwickler
Leiter Modulentwicklung
shoptimax GmbH
Guntherstraße 45 a
90461 Nürnberg
Amtsgericht Nürnberg HRB 21703
GF Friedrich Schreieck
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
***
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] OXID Unit-Tests - memory usage?
Hi list,
it seems that the test were running through now, although I can't really
tell... at the end there were debug outputs of huge arrays for at least
half an hour spamming my console :P
*Here is what I did to get it over the memory errors:*
- the email tests seem to require a configured mailserver which the OXVM
doesnt have, so after trying sendmail which didnt work without further
configuration, I installed postfix via:
/sudo apt-get install postfix/*
*
- but I still ran into Out Of Memory errors... which seemed to be caused
not by the overall memory limit, but script-related memory limits, so
I've edited the Apache php.ini configuration with
/sudo vi /etc/php5/apache2/php.ini/
and increased the memory limit to 512MB and max_execution_time to
240sec... and told phpunit to use this php.ini via
/oxPATH=/var/www/eshops/ce473/eshop/ php -d 'memory_limit=2048M' //*-c
/etc/php5/apache2/php.ini*///usr/bin/phpunit --verbose --bootstrap
bootstrap.php AllTestsUnit.php//
/
That seemed to do the trick ... but shouldn't be some reports generated
somewhere... couldn't find any coverage report or anything :(
Regards,
Stefan
Am 12.02.2013 13:13, schrieb Stefan Moises:
Hi Johannes,
thanks for your answer.
Hm, is that the exact command you are using? You do have a -d
Parameter in your example call ...
Did you install and configure sendmail on your system?
I have just tried your call and it hangs and exits again in
oxemailAzureTplTest :(
Thanks,
Stefan
Am 12.02.2013 12:45, schrieb Johannes Ackermann:
Hi Stefan,
Tests work for me when doing...
oxPATH='/var/www/eshop/' php -d 'memory_limit='2048M'
/usr/bin/phpunit --verbose --bootstrap bootstrap.php AllTestsUnit.php
(no oxAdmin_passwd, and no -d parameter)
My machine is a Ubuntu 12.04/Apache2/PHP5.3.
It also works with a lower memory limit (e.g. 1024M) -- no Out of
memory messages here.
Regards,
Johannes
-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von
Stefan Moises
Gesendet: Dienstag, 12. Februar 2013 09:00
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID Unit-Tests - memory usage?
Hi,
is nobody using the Unit tests? Are they working for anybody at the
moment?
Thanks,
Stefan
Am 08.02.2013 16:25, schrieb Stefan Moises:
Hi list,
I am trying to run all the OXID unit tests for the current CE version
using OXVM... although I have raised the used memory from 1024M to
2768M, I still get an out of memory error.. any ideas why? Has anybody
successfully tried to run the current test suite?
Here is the command I am using... my VM has currently 3328MB assigned.
oxPATH=/path/to/oxid/eshop/ oxADMIN_PASSWD='password' phpunit –d
'memory_limit=2768M' --verbose -–bootstrap bootstrap.php
AllTestsUnit.php
Call stack is:
...
Unit_Core_oxemailAzureTplTest
...PHP Fatal error: Out of memory (allocated -1998061568) (tried to
allocate 2013009921 bytes) in /usr/share/php/PHPUnit/Util/Type.php on
line 163 PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:52 PHP 3.
PHPUnit_TextUI_Command-run()
/usr/share/php/PHPUnit/TextUI/Command.php:147
PHP 4. PHPUnit_TextUI_TestRunner-doRun()
/usr/share/php/PHPUnit/TextUI/Command.php:214
PHP 5. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/TextUI/TestRunner.php:350
PHP 6. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:675
PHP 7. PHPUnit_Framework_TestSuite-runTest()
/usr/share/php/PHPUnit/Framework/TestSuite.php:732
PHP 8. OxidTestCase-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:757
PHP 9. PHPUnit_Framework_TestCase-run()
/var/www/eshops/ce473/unittests/unit/OxidTestCase.php:225
PHP 10. PHPUnit_Framework_TestResult-run()
/usr/share/php/PHPUnit/Framework/TestCase.php:653
PHP 11. PHPUnit_Framework_TestCase-runBare()
/usr/share/php/PHPUnit/Framework/TestResult.php:687
PHP 12. PHPUnit_Framework_TestCase-runTest()
/usr/share/php/PHPUnit/Framework/TestCase.php:706
PHP 13. ReflectionMethod-invokeArgs()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 14.
Unit_Core_oxInputValidatorTest-testCheckCountriesGoodCountries()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 15. PHPUnit_Framework_Assert::assertNull()
/var/www/eshops/ce473/unittests/unit/core/oxinputvalidatorTest.php:465
PHP 16. PHPUnit_Framework_Assert::assertThat()
/usr/share/php/PHPUnit/Framework/Assert.php:742
PHP 17. PHPUnit_Framework_Constraint-fail()
/usr/share/php/PHPUnit/Framework/Assert.php:1734
PHP 18. PHPUnit_Framework_Constraint-failureDescription()
/usr/share/php/PHPUnit/Framework/Constraint.php:91
PHP 19. PHPUnit_Util_Type::toString()
/usr/share/php/PHPUnit/Framework/Constraint.php:111
PHP 20. print_r() /usr/share/php/PHPUnit/Util/Type.php:163
No idea why it is only using 2 GB here though
Maybe it's an error trying to send mails which leads to this exception
... because I had to install
Re: [oxid-dev-general] OXID Unit-Tests - memory usage?
Hello OXID-Devs,
any news on this? I've heard of other OXID partners that the unit tests
are not working on the current OXID VM and that nobody can use it right
now for module certification etc.
Thanks,
Stefan
Am 12.02.2013 19:47, schrieb Stefan Moises:
Hi list,
it seems that the test were running through now, although I can't
really tell... at the end there were debug outputs of huge arrays for
at least half an hour spamming my console :P
*Here is what I did to get it over the memory errors:*
- the email tests seem to require a configured mailserver which the
OXVM doesnt have, so after trying sendmail which didnt work without
further configuration, I installed postfix via:
/sudo apt-get install postfix/*
*
- but I still ran into Out Of Memory errors... which seemed to be
caused not by the overall memory limit, but script-related memory
limits, so I've edited the Apache php.ini configuration with
/sudo vi /etc/php5/apache2/php.ini/
and increased the memory limit to 512MB and max_execution_time to
240sec... and told phpunit to use this php.ini via
/oxPATH=/var/www/eshops/ce473/eshop/ php -d 'memory_limit=2048M' //*-c
/etc/php5/apache2/php.ini*///usr/bin/phpunit --verbose --bootstrap
bootstrap.php AllTestsUnit.php//
/
That seemed to do the trick ... but shouldn't be some reports
generated somewhere... couldn't find any coverage report or anything :(
Regards,
Stefan
Am 12.02.2013 13:13, schrieb Stefan Moises:
Hi Johannes,
thanks for your answer.
Hm, is that the exact command you are using? You do have a -d
Parameter in your example call ...
Did you install and configure sendmail on your system?
I have just tried your call and it hangs and exits again in
oxemailAzureTplTest :(
Thanks,
Stefan
Am 12.02.2013 12:45, schrieb Johannes Ackermann:
Hi Stefan,
Tests work for me when doing...
oxPATH='/var/www/eshop/' php -d 'memory_limit='2048M'
/usr/bin/phpunit --verbose --bootstrap bootstrap.php AllTestsUnit.php
(no oxAdmin_passwd, and no -d parameter)
My machine is a Ubuntu 12.04/Apache2/PHP5.3.
It also works with a lower memory limit (e.g. 1024M) -- no Out of
memory messages here.
Regards,
Johannes
-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von
Stefan Moises
Gesendet: Dienstag, 12. Februar 2013 09:00
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID Unit-Tests - memory usage?
Hi,
is nobody using the Unit tests? Are they working for anybody at the
moment?
Thanks,
Stefan
Am 08.02.2013 16:25, schrieb Stefan Moises:
Hi list,
I am trying to run all the OXID unit tests for the current CE version
using OXVM... although I have raised the used memory from 1024M to
2768M, I still get an out of memory error.. any ideas why? Has anybody
successfully tried to run the current test suite?
Here is the command I am using... my VM has currently 3328MB assigned.
oxPATH=/path/to/oxid/eshop/ oxADMIN_PASSWD='password' phpunit --d
'memory_limit=2768M' --verbose ---bootstrap bootstrap.php
AllTestsUnit.php
Call stack is:
...
Unit_Core_oxemailAzureTplTest
...PHP Fatal error: Out of memory (allocated -1998061568) (tried to
allocate 2013009921 bytes) in /usr/share/php/PHPUnit/Util/Type.php on
line 163 PHP Stack trace:
PHP 1. {main}() /usr/bin/phpunit:0
PHP 2. PHPUnit_TextUI_Command::main() /usr/bin/phpunit:52 PHP 3.
PHPUnit_TextUI_Command-run()
/usr/share/php/PHPUnit/TextUI/Command.php:147
PHP 4. PHPUnit_TextUI_TestRunner-doRun()
/usr/share/php/PHPUnit/TextUI/Command.php:214
PHP 5. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/TextUI/TestRunner.php:350
PHP 6. PHPUnit_Framework_TestSuite-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:675
PHP 7. PHPUnit_Framework_TestSuite-runTest()
/usr/share/php/PHPUnit/Framework/TestSuite.php:732
PHP 8. OxidTestCase-run()
/usr/share/php/PHPUnit/Framework/TestSuite.php:757
PHP 9. PHPUnit_Framework_TestCase-run()
/var/www/eshops/ce473/unittests/unit/OxidTestCase.php:225
PHP 10. PHPUnit_Framework_TestResult-run()
/usr/share/php/PHPUnit/Framework/TestCase.php:653
PHP 11. PHPUnit_Framework_TestCase-runBare()
/usr/share/php/PHPUnit/Framework/TestResult.php:687
PHP 12. PHPUnit_Framework_TestCase-runTest()
/usr/share/php/PHPUnit/Framework/TestCase.php:706
PHP 13. ReflectionMethod-invokeArgs()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 14.
Unit_Core_oxInputValidatorTest-testCheckCountriesGoodCountries()
/usr/share/php/PHPUnit/Framework/TestCase.php:822
PHP 15. PHPUnit_Framework_Assert::assertNull()
/var/www/eshops/ce473/unittests/unit/core/oxinputvalidatorTest.php:465
PHP 16. PHPUnit_Framework_Assert::assertThat()
/usr/share/php/PHPUnit/Framework/Assert.php:742
PHP 17. PHPUnit_Framework_Constraint-fail()
/usr/share/php/PHPUnit/Framework/Assert.php:1734
PHP 18. PHPUnit_Framework_Constraint-failureDescription()
/usr/share/php/PHPUnit/Framework/Constraint.php:91
PHP 19. PHPUnit_Util_Type::toString
Re: [oxid-dev-general] Pros and cons for module-connectors
Hi,
yes, some type of dependency management is a must for the OXID module
system!
As a workaround, we have started a simple module managing dependencies
(smx_module_deps), at the moment you can only add other module ids
which your module depends on, e.g. in metadata.php you can add:
*'depends' = array(**
**'smx_filialabholung'**
**),*
'settings' = array(),
On our todo list are some more features like adding versions, e.g. like so
'depends' = array(
array('id' = 'smx_filialabholung', 'version' = '1.1'),
),
'settings' = array(),
What it does at the moment is simply to make sure that a module can't be
manually disabled if other modules depend on it. We have to extend that
so that the shop also doesn't automatically disable modules if
metadata.php has new extend entries etc.
But ideally, this should really be part of the OXID core
cheers,
Stefan
Am 21.01.2014 09:38, schrieb Joscha Krug | marmalade GmbH:
Hi,
same for me: I also don't like them. If you have dependencies between
modules go for composer or something the like.
Best would be if OXID could come up with an extension in the
metadata.php in which you could tell this module is based on that
other module.
Best regards
Joscha
//-
Joscha Krug
marmalade GmbH
www.marmalade.de http://www.marmalade.de/
k...@marmalade.de mailto:k...@marmalade.de
Leibnizstr.25
39104 Magdeburg
GERMANY
phone: +49 (0) 391 / 559 22 104
fax: +49 (0) 391 / 559 22 106
*OXMOB | mobile Template
http://www.oxmob.de/?pk_campaign=OXMOB%20%7C%20E-Mail-Linkpk_kwd=normalEmail*
Das einfach geniale OXID eShop Modul.
Ab sofort in unserem Online-Shop
http://www.marmalade.de/shop/Templates/OXMOB-OXID-eShop-mobile-Template.html?pk_campaign=OXMOB%20%7C%20E-Mail-Linkpk_kwd=normalEmail
erhältlich.
Am 21.01.2014 08:44, schrieb Marcel Müller:
Hey!
I don't like such additional connector modules. They have their own
bugs and generating system-wide errors, mostly. Especially when the
module has an own style and/or database tables far from oxid. I had
scenarios within a customer tried to remove a connectors modul and
gets a lot of trouble with the system. But if you want to get rich
with support, this could be a model ;)
What about a wrapper script inside every module or inside the vendor
structure? With that you can also check the versions and be agile.
*Mit freundlichen Grüßen*
Marcel Müller
Webentwicklung / Projektmanagement
eMail: m...@aikme.de mailto:m...@aikme.de
http://www.aikme.de/
aikme GmbH
Rheinstraße 43-45
55116 Mainz / Deutschland
Telefon: 06131 92 06 503
Telefax: 06131 92 08 334
www.aikme.de http://www.aikme.de/
aikme GmbH
Geschäftsführer: Sascha Coldewey
Sitz in Mainz, Registergericht: Mainz
Registernummer: HRB 44835
Umsatzsteuer ID: DE282561622
Am Dienstag, 21. Januar 2014 um 08:31 schrieb Roman Allenstein:
Hi folks,
me and my team are developing a concept for us, how to develop modules
for oxid. We are now at the point where we have to decide to develope a
connector-module for all our coming modules or not.
We know that some agecies use their own connector to integrate their
modules in oxid. And i am pretty unsure if this is the way to go
because
oxid provides a standardized way to integrate modules.
Whats your pros and cons for using an own connector?
Greets
Roman
--
Dipl.Winf. (FH) Roman Allenstein
Sales Manager E-Commerce
Spark 5 GmbH
Lutherstraße 7
27570 Bremerhaven
Fon: +49-471-4836-3547
Fax: +49-6151-8508-111
Mail: roman.allenst...@spark5.de mailto:roman.allenst...@spark5.de
Web: http://www.spark5.de
--
Geschäftsführer:
Dipl. Designer Till Middelhauve
Dipl. Informatiker Witold Wegner
Amtsgericht Darmstadt, HRB 7809
Diese E-Mail könnte vertrauliche und/oder rechtlich geschützte
Informationen enthalten. Wenn Sie nicht der richtige Adressat sind oder
diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort
den
Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie
die unbefugte Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and destroy this e-mail.
Any
unauthorised copying, disclosure or distribution of the material in
this
e-mail is strictly forbidden.
___
dev-general mailing list
dev-general@lists.oxidforge.org mailto:dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
--
Mit den besten Grüßen aus Nürnberg,
Stefan Moises
[oxid-dev-general] More flexible handling for module templates and blocks
Hi, I have made a proposal for some module enhancements, especially concerning module templates and blocks for subshops and for giving shop owners the ability to safely override module templates and blocks: https://bugs.oxid-esales.com/view.php?id=5767 What do you think? Is something like this already planned for the next evolution of the module system? Cheers, Stefan -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Ulmenstrasse 52 H 90443 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
Re: [oxid-dev-general] More flexible handling for module templates and blocks
Hi OXID-Devs, now that the OXID Commons is over, maybe we could start discussing this? :) We really need a good solution for subshop module templates and also for customized module templates so what do you think of this proposal? Thanks, Stefan Am 20.05.2014 10:49, schrieb Stefan Moises: Hi, I have made a proposal for some module enhancements, especially concerning module templates and blocks for subshops and for giving shop owners the ability to safely override module templates and blocks: https://bugs.oxid-esales.com/view.php?id=5767 What do you think? Is something like this already planned for the next evolution of the module system? Cheers, Stefan -- Mit den besten Grüßen aus Nürnberg, Stefan Moises *** Stefan Moises Senior Softwareentwickler Leiter Modulentwicklung shoptimax GmbH Ulmenstrasse 52 H 90443 Nürnberg Amtsgericht Nürnberg HRB 21703 GF Friedrich Schreieck Fax: 0911/25566-29 moi...@shoptimax.de http://www.shoptimax.de *** ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
OXID 6 AJAX Popups in modules
Hi fellow v6 users,
I get a CLASSNOTFOUND error if I try to open a custom AJAX Popup in the
v6 Backend:
/[03 Nov 15:54:52.660799 2017] [exception] [type
OxidEsales\Eshop\Core\Exception\SystemComponentException] [code 0] [file
/var/www/html/oxid6_demo/vendor/oxid-esales/oxideshop-ce/source/Core/UtilsObject.php]
[line 238] [message EXCEPTION_SYSTEMCOMPONENT_CLASSNOTFOUND
shoptifind_landingpages_ajax]/
I am pretty sure I have setup everything correctly in my metadata.php,
cause the other 99,9% of the module are working... ;)
$sMetadataVersion= '2.0';
/'controllers' => array(//
// 'shoptifind_landingpages' =>
Shoptimax\Shoptifind\Application\Controller\Admin\ShoptifindLandingpages::class,//
// 'shoptifind_landingpages_ajax'=>
Shoptimax\Shoptifind\Application\Controller\Admin\ShoptifindLandingpagesAjax::class,/
I've got a namespaced class:
/namespace Shoptimax\Shoptifind\Application\Controller\Admin;//
///**//
// * Ajax component//
// *///
//class ShoptifindLandingpagesAjax extends
\OxidEsales\Eshop\Application\Controller\Admin\ListComponentAjax//
//{/
and for all other classes in front- and backend the autoloading etc. is
working fine...
/"autoload": {//
// "psr-4": {//
// "Shoptimax\\Shoptifind\\":
"../../../source/modules/shoptimax/shoptifind"//
// }//
// }/
So, to me it seems that the "controllers" aliases aren't really
available at this stage when trying to load the popup via the
"shoptifind_landingpages_ajax" alias... any ideas?
Thanks a lot,
Stefan
--
--
Stefan Moises
Manager Research & Development
shoptimax GmbH
Ulmenstraße 52 H
90443 Nürnberg
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
Re: OXID 6 AJAX Popups in modules
Hi Benjamin,
thanks - yeah, that sounds exactly like my problem ... too bad it is
already open since July :(
Hopefully this will be fixed soon!
Cheers,
Stefan
Am 04.11.17 um 14:32 schrieb Benjamin Joerger:
Hello Stefan,
I guess this is a bug which is already
reported https://bugs.oxid-esales.com/view.php?id=6668
Cheers
*Gesendet:* Freitag, 03. November 2017 um 17:01 Uhr
*Von:* "Stefan Moises" <moi...@shoptimax.de>
*An:* "dev-general@lists.oxidforge.org" <dev-general@lists.oxidforge.org>
*Betreff:* OXID 6 AJAX Popups in modules
Hi fellow v6 users,
I get a CLASSNOTFOUND error if I try to open a custom AJAX Popup in
the v6 Backend:
/[03 Nov 15:54:52.660799 2017] [exception] [type
OxidEsales\Eshop\Core\Exception\SystemComponentException] [code 0]
[file
/var/www/html/oxid6_demo/vendor/oxid-esales/oxideshop-ce/source/Core/UtilsObject.php]
[line 238] [message EXCEPTION_SYSTEMCOMPONENT_CLASSNOTFOUND
shoptifind_landingpages_ajax]/
I am pretty sure I have setup everything correctly in my metadata.php,
cause the other 99,9% of the module are working... ;)
$sMetadataVersion= '2.0';
/'controllers' => array(/
/ 'shoptifind_landingpages' =>
Shoptimax\Shoptifind\Application\Controller\Admin\ShoptifindLandingpages::class,/
/ 'shoptifind_landingpages_ajax'=>
Shoptimax\Shoptifind\Application\Controller\Admin\ShoptifindLandingpagesAjax::class,/
I've got a namespaced class:
/namespace Shoptimax\Shoptifind\Application\Controller\Admin;/
//**/
/ * Ajax component/
/ *//
/class ShoptifindLandingpagesAjax extends
\OxidEsales\Eshop\Application\Controller\Admin\ListComponentAjax/
/{/
and for all other classes in front- and backend the autoloading etc.
is working fine...
/"autoload": {/
/ "psr-4": {/
/ "Shoptimax\\Shoptifind\\":
"../../../source/modules/shoptimax/shoptifind"/
/ }/
/ }/
So, to me it seems that the "controllers" aliases aren't really
available at this stage when trying to load the popup via the
"shoptifind_landingpages_ajax" alias... any ideas?
Thanks a lot,
Stefan
--
--
Stefan Moises
Manager Research & Development
shoptimax GmbH
Ulmenstraße 52 H
90443 Nürnberg
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
--
--
Stefan Moises
Manager Research & Development
shoptimax GmbH
Ulmenstraße 52 H
90443 Nürnberg
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shoptimax.de
http://www.shoptimax.de
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
Re: OXID 6 - Activating a module in multiple subshops programatically
Hey again,
any other input, maybe from an OXID core developer? :)
I don't think it is a problem with setShopId(), since it worked pretty
well up to OXID 5.3.x ...
How would I activate modules in multiple subshops in a loop, without
getting that
ERROR_METADATA_CONTROLLERS_NOT_UNIQUE
error in Oxid 6?
Thank you very much,
best regards,
Stefan
Am 06.02.18 um 18:29 schrieb K1 G.:
Hi Stefan,
only a guess by having a quick look at the code you showed:
config->setShopId is not a good idea. It will not reload the config
object for current the process. So you will have a mix config objects
and configuration values from different shops.
I know that oxid console is using something like "shopspecificconfig"
class to ensure loading the correct config for a given shop id but
even with that you need often to call setConfig on different objects
and the registry.
I would suggest to debug and check the config objects to ensure you
have the correct config loaded.
best regards
K1
Am 06.02.2018 13:22 schrieb "Stefan Moises" <moi...@shoptimax.de
<mailto:moi...@shoptimax.de>>:
Hi there,
in OXID EE 5.3.x we were using a util class to activate modules
based on whitelist/blacklist for multiple subshops.
For OXID 6, that is not working 100% anymore, if a module defines
its own "controllers" in metadata.php, e.g.
https://github.com/OXIDprojects/oxid-module-internals
<https://github.com/OXIDprojects/oxid-module-internals>
'controllers'=> [
'module_internals_metadata'=>
\OxidCommunity\ModuleInternals\Controller\Admin\Metadata::class,
'module_internals_state'=>
\OxidCommunity\ModuleInternals\Controller\Admin\State::class,
'module_internals_utils'=>
\OxidCommunity\ModuleInternals\Controller\Admin\Utils::class,
],
Now if I use this class
https://github.com/shoptimax/ioly_installer/blob/master/IolyInstallerCore.php#L450
<https://github.com/shoptimax/ioly_installer/blob/master/IolyInstallerCore.php#L450>
and ModuleInstaller::activate($oModule):
/ foreach ($aShopIds as $shopId) {//
// try {//
//$oConfig->setShopId($shopId);//
// $oModule = oxNew('oxModule');//
// if ($oModule->load($sModuleId)) {//
// $oModuleCache = oxNew('oxModuleCache',
$oModule);//
// $oModuleInstaller =
oxNew('oxModuleInstaller', $oModuleCache);//
//*if ($oModuleInstaller->activate($oModule)) {*/
...
to activate the module for multiple subshops, I get an *exception*
after the first subshop, e.g.
/Loaded moduleinternals module, trying to activate ...//
//Error activating module 'moduleinternals': Fehler: Modul nicht
aktiviert.In einem Shop oder Sub-Shop müssen Schüssel und
Werte für "controllers" eindeutig sein.Folgende Schlüssel
oder Werte für "controllers", die in der Datei metadata.php dieses
Moduls definiert sind, existieren schon im Shop:
OxidCommunity\ModuleInternals\Controller\Admin\Metadata,OxidCommunity\ModuleInternals\Controller\Admin\State,OxidCommunity\ModuleInternals\Controller\Admin\Utils//
//#0 /var/www/html/demo-oxid6/source/oxfunctions.php(103):
OxidEsales\EshopCommunity\Core\UtilsObject->oxNew('OxidEsales\\Esho...')//
//#1
/var/www/html/demo-oxid6/vendor/oxid-esales/oxideshop-ce/source/Core/Module/ModuleInstaller.php(100):
oxNew('OxidEsales\\Esho...')//
//#2
/var/www/html/demo-oxid6/vendor/ioly/installer/IolyInstallerCore.php(450):
OxidEsales\EshopCommunity\Core\Module\ModuleInstaller->activate(Object(OxidCommunity\ModuleInternals\Core\Module))//
//#3
/var/www/html/demo-oxid6/vendor/ioly/installer/IolyInstallerCore.php(417):
ioly\IolyInstallerCore::activateModule('moduleinternals', '1')//
//#4
/var/www/html/demo-oxid6/vendor/ioly/installer/IolyInstallerCore.php(184):
ioly\IolyInstallerCore::activateModulesWhitelisted()//
//#5 /var/www/html/demo-oxid6/source/install.php(27):
ioly\IolyInstallerCore::run('/var/www/html/g...', false, false,
false)//
//#6 {main}/
So it seems to work for the first subshop, but then the check for
"duplicate" controllers throws an Exception.
Any idea how to fix this? It seems that the ModuleInstaller isn't
aware of the different subshop ... I've also tried to set the
Config with e.g.
$oModuleInstaller->setConfig($oConfig);
etc., but that didn't help either.
Thanks,
Stefan
--
--
Stefan Moises
Manager Research & Development
shoptimax GmbH
Ulmenstraße 52 H 90443 Nürnberg
<https://maps.google.com/?q=Ulmenstra%C3%9Fe+52+H+90443+N%C3%BCrnberg=gmail=g>
Tel.: 0911/25566-0
Fax: 0911/25566-29
moi...@shop
