Hi,
You don't need to set every field manually.
Your code snippet works and creates new category.
In your code i see only notice message (not a warning) ignored by oxid's error
reporting settings.
Alf.
-Original Message-
From: dev-general-boun...@lists.oxidforge.org on behalf of Cubr
Hi,
From: "Christopher Simon"
in my last mail i mentioned the way of "generating" the file by an
autoinstaller with var_export (which produces valid php code) and
file_put_contents. Also, the file could be generated with an shop Id, or
we could use the same file for all shops with different a
Hi,
Am 08.11.2010 14:10, schrieb Sarunas Valaskevicius:
Still, the mentioned downside about the module installer is a heavy one
- moving the module class configs could be thought as going to the
opposite direction.
in my last mail i mentioned the way of "generating" the file by an
autoinst
Hi,
moving config values for modules to a file makes sense and improves the
developing experience only for these two reasons:
1) it would be possible to create module classes for some early loaded eShop
core classes;
2) it would be possible to disable modules if admin does not load because of
Hi everybody,
jkrug started an interesting check list on this wiki page:
http://wiki.oxidforge.org/Check_before_going_live
Feel free to add more ideas!
Regards
Marco
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gman
Hi everybody,
today, we published Security Bulletin 2010-006:
http://wiki.oxidforge.org/Security_bulletins/2010-006
All partners and support contract owners have already been informed.
The issue has been resolved in OXID eShop version 4.4.4. If you cannot
update for any reason, please fix it ASAP
