Re: [oxid-dev-general] new module handling

2013-01-27 Thread Joscha Krug | marmalade.de
Hello Saulius,

thanks for your reply.

Well a parameter to prevent modules from self-deactivation could be a
solution. Although i'm pretty sure that you would find that in almost
any installationsit will be turned off. ;-)


 Module id must NOT be the same as module directory name as there is
relationship between module id and module root
 directory saved in database. Furthermore as module id and module
directory path must be unique we recommend
 using directory name and vendor directory name for module id.
A ok. That leads to problems in some of our installations. Iwill come
back if i could reproduce that.Good to hear thatwe ot the id right.

Best Joscha

//-
 
Joscha Krug
marmalade.de e.K.
 
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

-
Besuchen Sie das *eCommerceCamp 2013*

vom 15. bis 17. März an der Ernst-Abbe-Fachhochschule Jena

http://www.ecommerce-camp.de/

Am 15. März ist es soweit! Dann startet das erste deutsche
eCommerceCamp. Wir möchten Entwickler und Integratoren von Open-Source
Shopsystemen, wie z.B. Magento, OXID oder Shopware, sowie Interessierte
für ein Wochenende im Stil der Web 2.0 Barcamps zusammenbringen. Damit
wollen wir den Teilnehmern eine Plattform für den informellen Austausch
von Know-how und Erfahrungen bereitstellen. Vorträge, Präsentationen,
Workshops und Diskussionsrunden von und mit den Teilnehmern bestimmen
dabei das Tagesprogramm.
-
Am 22.01.2013 10:53, schrieb Saulius Stasiukaitis:

 Hello Joscha,

  

 Nice to hear you like the way we lead our modules to. Discussion about
 module handling is very welcome as we can get information from real
 field what is hard to do while sitting mostly just near shop core.

 I'll try to take your letter peace by peace and response to them.

 / /

 /But it gets very hard sometimes, like when modules deactivate
 themselves or you get those strange red bars in the backend.

 After that, you store some of the metadata informations in the
 database. Why? If you remove some of the classes, files,... your
 module leads to those strange red entries as mentioned before. I think
 you had good reasons to do so - could you explain them? Maybe we
 together find another solution that is cleaner and doesn't need that
 double-storeing thing./

 You probably talk about feature, when shop does not find module class.
 Instead of returning fatal error shop deactivate module and mark it
 with red bars. So it should be visible that module need to be checked
 for errors. We save to database because it is simple and comfortable
 solution to work with.  Another solution would be scan file system on
 every load. This is much less effective performance and effort approach.

  


 /And - i think thats the worst feature - there is that
 self-deactivating: Is see your idea but i think it breaks more than it
 helps.
 We often develop modules (like many other agencies as well i guess)
 that keep lots of helpers for one project. So in that module you have
 an extension for oxarticle, for details, start, for the checkout,...
 so now it comes to the point that something is broken in some special
 cases let's say in the checkout for example. Now the shop deactivates
 the module and baaammm oxarticle, details, start,... will also be
 broken in ANY way!/

 This is done to prevent from fatal errors. But from responses it looks
 that current solution isn't the most effective. Maybe we could improve
 this place by:
 deactivate only corrupted class, not whole module.
 do not deactivate if parameter iDebug has value -1
 add additional parameter that turn of auto deactivation.

 What is your opinion about those suggestions? Can you describe in
 which scenarios auto deactivation hurts most in developing process or
 in productive mode.

 / /


 /What i don't like is that the ModuleID must be exactly the module
 path. This is simply redundant.
 Either you want to have the module path, then we should not set it
 again OR it is an own key like a module-identifier that is unique in
 the OXID world (maybe there could be a central repository where you
 could register new ones) - which i think is the right way./

 Module id must NOT be the same as module directory name as there is
 relationship between module id and module root directory saved in
 database. Furthermore as module id and module directory path must be
 unique we recommend using directory name and vendor directory name for
 module id.


 /Then, there is a missing feature in my opinion: Dependencies to other
 modules. Could be an easy array, but would often help a lot./

 This suggestion is on our sight for some time. We found it very
 interesting as something we should implement. Before starting

Re: [oxid-dev-general] little nice module

2013-01-27 Thread Joscha Krug | marmalade.de
Hi Saulius,

thank's for sharing that helper module!

Joscha

//-
 
Joscha Krug
marmalade.de e.K.
 
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

-
Besuchen Sie das *eCommerceCamp 2013*

vom 15. bis 17. März an der Ernst-Abbe-Fachhochschule Jena

http://www.ecommerce-camp.de/

Am 15. März ist es soweit! Dann startet das erste deutsche
eCommerceCamp. Wir möchten Entwickler und Integratoren von Open-Source
Shopsystemen, wie z.B. Magento, OXID oder Shopware, sowie Interessierte
für ein Wochenende im Stil der Web 2.0 Barcamps zusammenbringen. Damit
wollen wir den Teilnehmern eine Plattform für den informellen Austausch
von Know-how und Erfahrungen bereitstellen. Vorträge, Präsentationen,
Workshops und Diskussionsrunden von und mit den Teilnehmern bestimmen
dabei das Tagesprogramm.
-
Am 25.01.2013 11:19, schrieb Saulius Stasiukaitis:

 Hi,

 One of OXID developer makes a little nice module which helps us with
 modules developing. Feel free to try it and use it if you like.

 https://github.com/acirtautas/oxid-module-internals

  

 Saulius Stasiukaitis

 OXID developer

  



 ___
 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

[oxid-dev-general] new module handling

2013-01-20 Thread Joscha Krug | marmalade.de
Dear OXID Core-Team,

now we've used the new module system in many projects.
It makes activating and deactivating in most cases very easy.

But it gets very hard sometimes, like when modules deactivate themselves
or you get those strange red bars in the backend.

What are my thoughts about all that:

I think the metadata.php helps a lot and is the right place for the base
configuration. Great job!

What i don't like is that the ModuleID must be exactly the module path.
This is simply redundant.
Either you want to have the module path,then we should not set it again
OR it is an own key like a module-identifier that is unique in the OXID
world (maybe there could be a central repository where you could
register new ones) - which i think is the right way.

After that, you store someof the metadata informations in the database.
Why? If you remove some of the classes, files,... your module leads to
those strange red entries as mentioned before. I think you had good
reasons to do so - could you explain them? Maybe we together find
another solution that is cleaner and doesn't need that double-storeing
thing.

Then, there is amissing featurein my opinion: Dependencies to other
modules. Could be an easy array, but would often help a lot.

And - i thinkthats the worst feature - there is that self-deactivating:
Is see your idea but i think it breaks more than it helps.
We often develop modules (like many other agencies as well i guess) that
keep lots of helpers for one project. So in that module you have an
extension for oxarticle, for details, start, for the checkout,... so now
it comes to the point that something is broken in some special cases
let's say in the checkout for example. Now the shop deactivates the
module and baaammm oxarticle, details, start,... will also be broken
in ANY way!

Hope to start a fruitful and constructive discussion.

Best,

Joscha


-- 

//-
 
Joscha Krug
marmalade.de e.K.
 
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

-
Besuchen Sie das *eCommerceCamp 2013*

vom 15. bis 17. März an der Ernst-Abbe-Fachhochschule Jena

http://www.ecommerce-camp.de/

Am 15. März ist es soweit! Dann startet das erste deutsche
eCommerceCamp. Wir möchten Entwickler und Integratoren von Open-Source
Shopsystemen, wie z.B. Magento, OXID oder Shopware, sowie Interessierte
für ein Wochenende im Stil der Web 2.0 Barcamps zusammenbringen. Damit
wollen wir den Teilnehmern eine Plattform für den informellen Austausch
von Know-how und Erfahrungen bereitstellen. Vorträge, Präsentationen,
Workshops und Diskussionsrunden von und mit den Teilnehmern bestimmen
dabei das Tagesprogramm.
-
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] EE Staging to Live

2013-01-11 Thread Joscha Krug | marmalade.de
Dear Devs,

as i set up the Staging-Enivronment on our actual project i entered the
Licence-Key.
After the logout i got the following message Funktionalität ist im
Staging-Modus eingeschränkt(reduced functionality in staging-mode). See
attached screenshot.

Isn't the idea of a staging-system that you have a nearly exact copy of
your shop so you could be shure if it works there, it will also work in
your live-system?

Could you tell about the differences?

Thank you and have a nice weekend

Joscha

-- 

//-
 
Joscha Krug
marmalade.de e.K.
 
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.

attachment: staging.png___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Forbid the public access to a php.ini in shop .htaccess

2012-11-09 Thread Joscha Krug | marmalade.de
Hi Björn,

ithink this is a great improvement by just adding two or three lines in
the .htaccess.

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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 09.11.2012 10:34, schrieb Lange, Björn:
 Good Morning,

 The OXID-Team closed the request
 https://bugs.oxid-esales.com/view.php?id=4303, but i still want to
 discuss it. Maybe the OXID team got me wrong.

 1und1 suggested, to put a php.ini in the shop root, to enable the zend
 optimizer (1und1 removed the deep
 link 
 http://hilfe-center.1und1.de/archiv-c82642/zend-optimizer-c82694/wie-kann-ich-den-zend-optimizer-verwenden-a783269.html).

 So People have a public php.ini in there shop, and a possible
 information disclosure. 1und1 did not tell, how to change the
 .htaccess to prevent this. I think, this is a common use case for
 hosters und i would suggest, that OXID adds a deny-rule for a php.ini
 the shop root, additionally to the log files etc.

 What do you think?

 Regards,
 Björn

 -- 

 *_
 WBL Konzept, Beerden  Lange GbR*
 *Björn Lange*
 Geschäftsführender Gesellschafter
  
 Luxemburger Straße 266
 50937 Köln

 Bilker Straße 34
 40213 Düsseldorf

 Telefon: 0211 942 120 30 *|* Fax:  0211 942 120 32
 www.wbl-konzept.de
 http://www.wbl-konzept.de/ *|* www.facebook.com/wbl.konzept
 http://www.facebook.com/wbl.konzept *|* b.la...@wbl-konzept.de
 mailto:b.la...@wbl-konzept.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

Re: [oxid-dev-general] Release candidate 1 for OXID eShop version 4.7/5.0

2012-10-11 Thread Joscha Krug | marmalade.de
Hi guys,

thanks for the new version.
I checked it out.

There are a few questions and hints:

1) Why are Frontend-Controllers directly in application/controllers
while controllers for the backend are in the subfolder /admin? In
application/views you have separated the folders.

2) I have seen that Smarty-Templates are moved to
application/views/tplname while static files to that template still in
out/tplname. If you want to sell ready-made templates that makes
everything more complicated.

3) You changed the template-structure from 4.4.8 to 4.5 and now again to
4.7 / 5.0. Again: If you want to sell ready made templates, like we do
with our mobile Template oxmob.de, that means that there is absolutely
no chance to keep them updated without maintaining separate versions!
Please:Think, how you want to change it - move the files and then leave
them, where they are! Keep the API stable. Keep in mind, that if your
changes are that huge, you will definitivly BREAK things.

4) A feature request according to that would be a more powerful template
inheritance to have three levels (your template - bought template -
azure/basic). Already send that to Erik.

So, keep up the good work but have in mind what the cosequences are for
your partners.

Best Joscha



//-
 
marmalade.de
Joscha Krug
 
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 11.10.2012 21:54, schrieb Marco Steinhaeuser:
 Hi everybody,

 RC1 is out for OXID eShop version 4.7/5.0.
 Same place for information and links to downloads:
 http://wiki.oxidforge.org/Downloads/4.7.0_5.0.0

 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

Re: [oxid-dev-general] Nested Sets and OXSORT

2012-07-17 Thread Joscha Krug | marmalade.de
Hi Daniel,

 using nested sets AND parent_id's makes the code hard to understand.
 You are mixing to different concepts which also doubles potential
error pits.

You've nailed it! Thats what i wanted to say. I can go with both
concepts alone. But mixing them is really strange! Although you could
enter OXSORT also for subcategories.

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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.
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] OXID-CE and the 'community'.

2012-07-16 Thread Joscha Krug | marmalade.de
+1 for a Github-Repo for CE

We've got the first patches for TOXID cURL and it is great just to
review them and merge with a click.

Joscha

//-
 
marmalade.de
Joscha Krug
 
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 16.07.2012 17:20, schrieb Dave J. Holloway:
 Hi Adrian,

 Thanks for the answer. Your link didn't work, but I found it here:
 http://permalink.gmane.org/gmane.comp.php.oxid.general/1697

 Here's the excerpt:

 Hello Adrian,

 do you know the word You can't catch two birds with one stone? :-))

 Basically, OXID projects is a totally different topic to moving the core to 
 GitHub. Anyway, we already have that in our back heads. Maybe a good first 
 step would be to use GitHub as a mirror instead of the public SVN where we 
 mirror the development SVN now on a nightly basis:
 http://svn.oxid-esales.com/

 But also this step needs evaluation, thinking about the processes and some 
 effort within the infrastructure. That's why I can't promise any time frame 
 for that.

 Thanks for your idea anyway :-)

 Marco

 What a shame. I think OXID are missing out on a lot of 'free
 development' from the community. It doesn't even need to be GitHub. A
 standalone git server (just git, not github) over HTTP would do just
 fine. I assume that would get around any licensing issues. They could
 use public branches for CE and private clones for PE/EE.

 @Marco what do you think? Have there been any further developments on this?


 Dave



 Am 16.07.12 16:56, schrieb Adrian Kirchner:
 Hi Dave,

 I asked for Github migration in april this year and I think Marcos
 answer is still the last official answer to this topic:
 http://www.mail-archive.com/dev-general@lists.oxidforge.org/msg01602.html



 Best regards

 Adrian

 ___
 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

[oxid-dev-general] Nested Sets and OXSORT

2012-07-16 Thread Joscha Krug | marmalade.de
Hi,

today we discussed the oxcategories-structure.

We are wondering why there is a oxsort field.
As told everywhere, OXID uses nested sets for building the categorytree.
So normaly you don't need a manual sorting-field.

Could you explain why you not just rely on them?

Best Joscha

-- 

//-
 
marmalade.de
Joscha Krug
 
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.

___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Nested Sets and OXSORT

2012-07-16 Thread Joscha Krug | marmalade.de
Ok, seems like OXID is NOT using nested sets?!

The question is more like: Why do we have left+right although we use
ParentID and Sorting?
Isn't that a bit too redundant?

Regards,
Joscha

//-
 
marmalade.de
Joscha Krug
 
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 16.07.2012 19:31, schrieb Björn Lange:
 Hi All,

 2012/7/16 Frank Zunderer frank.zunde...@zunderer.de
 mailto:frank.zunde...@zunderer.de

 i think nested sets are not used for building the categorytree,
 it's built from id/parentid.


 And the sorting becomes easier, because every category with oxparent =
 'oxrootid' has oxleft=1 at the moment.

 Regards,
 Björn

 -- 

 *_
 WBL Konzept, Beerden  Lange GbR*
 *Björn Lange*
 Geschäftsführender Gesellschafter
  
 Luxemburger Straße 266
 50937 Köln

 Bilker Straße 34
 40213 Düsseldorf

 Telefon: 0211 942 120 30 *|* Fax: 0211 192 120 32
 www.wbl-konzept.de
 http://www.wbl-konzept.de/ *|* www.facebook.com/wbl.konzept
 http://www.facebook.com/wbl.konzept *|* b.la...@wbl-konzept.de
 mailto:b.la...@wbl-konzept.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

Re: [oxid-dev-general] blShowFinalStep will be ditched from OXID eShop

2012-06-29 Thread Joscha Krug | marmalade.de
Hi,

well, it is still in use in some older templates that are migrated from
version  4.5.

So please keep at least an getter for backwards compatibility or provide
a small module for those shops.

Have a nice weekend

Joscha

//-
 
marmalade.de
Joscha Krug
 
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
Am 29.06.2012 16:21, schrieb Marco Steinhaeuser:
 Hi everybody,

 remember the possibility to switch between 4 and 5 order steps? It
 doesn't work any longer in Azure template and was recorded as a bug:
 https://bugs.oxid-esales.com/view.php?id=3283

 After a few internal discussions, we decided to ditch that option at
 all: we believe that it is not used any longer in 2012. Also, we
 didn't hear much about this effect ;)

 Have a nice week end!
 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

[oxid-dev-general] Modulehandling with Version 4.6

2012-06-18 Thread Joscha Krug | marmalade.de
Dear OXID Developer,

first let's say: It feals absolutely right to enable / disable modules
with a single click. Great.

Anyway, with have with all our modules massive problems with the new
handling.

Let's have a look on our mobile Template-Module:

marm/mobiletemplate/metadata.php

?php

/**
 * Metadata version
 */
$sMetadataVersion = '1.0';
 
/**
 * Module information
 */
$aModule = array(
'id'   = 'oxmob',
'title'= 'OXMOB :: mobile Template',
'description'  = 'mobile Template for OXID eShopbased on jQuery
Mobile',
'version'  = '1.3.0',
'author'   = 'marmalade.de :: Joscha Krug',
'url'  = 'http://www.marmalade.de',
'email'= 'm...@marmalade.de',
'extend'   = array(
'payment'=
'marm/mobiletemplate/marm_mobiletemplate_payment',
'start'=
'marm/mobiletemplate/marm_mobiletemplate_start',
'marm_themeswitcher' =
'marm/mobiletemplate/marm_themeswitcher_mobile',
'oxlang'=
'marm/mobiletemplate/marm_themeswitcher_oxlang',
'oxshopcontrol' =
'marm/mobiletemplate/marm_themeswitcher_oxshopcontrol',
),
'files' = array(
),
'blocks' = array(
),
   'settings' = array(
)
);

Problem:
If you install the module, everything is fine. If you then deaktivate it
and want to activate it again, it fails.

The only solution:
Copy all module-files into another directory, andjust the module paths
and activate the module.

Strange behaviour! Could you explain, where the settings are cached?
Could you see, what we're doing wrong?

Best Joscha

-- 

//-
 
marmalade.de
Joscha Krug
 
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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Modulehandling with Version 4.6

2012-06-18 Thread Joscha Krug | marmalade.de
Hi,

thanks for your hint.

 I think the new Module handler doesnt like when you portable modules
 from an older Version to 4.6 and then make an new meta.php file for
 this without deleten the old one befor.
 Just my idea...
Happens also on fresh installations with version 4.6.x

Seems like there are some checks, that break the re-activating.

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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
Am 18.06.2012 16:49, schrieb Bernd Hasis:


___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Regular cleanup

2012-06-12 Thread Joscha Krug | marmalade.de
Hi Vilma,

jepp, we use them in some shops. Could you explain a bit more, why you
would remove those methods?
Any problems with that? Or just a cleanup?

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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

Am 12.06.2012 09:15, schrieb Vilma Liorensaityte:
 Hi all,

 we are performing regular cleanup and collecting information about 
 promotions. Do you use these promotions

  - Our Bargain! with id oxfirststart from CMS pages (Admin-Customer 
 Info-CMS Pages)
 Or 
  - Top offer start page with id oxtopstart (Admin-Customer 
 Info-Promotions)?

 We would appreciate for your help,
 Vilma
 ___
 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

Re: [oxid-dev-general] Regular cleanup

2012-06-12 Thread Joscha Krug | marmalade.de

  
  
Don't miss
the getter!

  
  
  //-
  
  marmalade.de
  Joscha Krug
  
  www.marmalade.de
  k...@marmalade.de
  
  
Leibnizstr.25
  39104 Magdeburg
  GERMANY
  
  phone: +49 (0) 391 / 559 22 104
  fax: +49 (0) 391 / 559 22 106



Am 12.06.2012 10:42, schrieb Alexander Kludt:

  
  Hi,
  
  we are using them on a regular base as well, but if you just want
  to remove them from a fresh install i see no problem with that.
  -- 



mit freundlichen Gren
Alexander Kludt


__
Phone: 09283-5925453
Fax: 09283-592671
Skype: kingschnulli
Email: cod...@aggrosoft.de
Website: www.aggrosoft.de

__
Aggrosoft it intelligence GbR
Tannstrasse 12
95111 Rehau
GERMANY

Sitz Rehau, Amtsgericht Hof
Steuernummer: 223/165/54508
Ust.-Id. Nr. gem  27 a Umsatzsteuergesetz: DE260722773

___
Diese Nachricht ist nur fr den Empfnger () bestimmt, sollten
Sie nicht der Empfnger sein lschen Sie diese Nachricht
umgehend und geben Sie uns bitte per Email (cod...@aggrosoft.de)
Bescheid
ber den flschlichen Erhalt. 

  
  
  
  

  


  

  
  Joscha Krug |
  marmalade.de
12. Juni 2012 10:10

  


  
  Hi
  Vilma,
  
  jepp, we use them in some shops. Could you explain a bit
  more, why you would remove those methods?
  Any problems with that? Or just a cleanup?
  
  Best Joscha
 
  ___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
  


  

  
  Vilma
  Liorensaityte
12. Juni 2012 09:15

  


  Hi all,

we are performing regular cleanup and collecting information
about promotions. Do you use these promotions

- "Our Bargain!" with id oxfirststart from CMS pages
(Admin-Customer Info-CMS Pages)
Or 
- "Top offer start page" with id oxtopstart
(Admin-Customer Info-Promotions)?

We would appreciate for your help,
Vilma
___
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

  

___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Release Candidate 1 published today

2012-04-23 Thread Joscha Krug | marmalade.de
Ha,

that was time, downloaded it 30 Minutes ago!
Will try it and test all our modules with it.

Thank you very much!

Joscha

//-
 
marmalade.de
Joscha Krug
 
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

Am 23.04.2012 12:11, schrieb Marco Steinhaeuser:
 Hi,


  still no updatescript?

 Here you go. I just uploaded a package that helps you updating your
 OXID eShop CE 4.5.9 to 4.6.0 Release Candidate:
 http://www.oxid-esales.com/de/exchange/extensions/oxid-eshop-460-beta?tab=get-extension

 The aim is that you can check the Release Candidate in your very own
 environment with your own data. The update package is _not_ supposed
 to be used in a working environment, just developers may use it for
 testing purposes until the final release will be published. Also
 please note, that this is a draft update package, not containing any
 README etc...

 Good luck!
 Marco

 **

 
 *From:* dev-general-boun...@lists.oxidforge.org
 [dev-general-boun...@lists.oxidforge.org] on behalf of Joscha Krug |
 marmalade.de [k...@marmalade.de]
 *Sent:* Tuesday, April 17, 2012 2:48 PM
 *To:* dev-general@lists.oxidforge.org
 *Subject:* Re: [oxid-dev-general] Release Candidate 1 published today

 Hi Marco,

 still no updatescript?

 So no chance to test with real data. Right?

 Best Joscha

 //-
  
 marmalade.de
 Joscha Krug
  
 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

 Am 17.04.2012 14:44, schrieb Marco Steinhaeuser:
 Hi,

 today, RC1 was published. You may download it from this page:
 http://www.oxid-esales.com/de/exchange/extensions/oxid-eshop-460-beta

 Also, the demo was updated on
 http://demoshop.oxid-esales.com/beta/community-edition/

 Please note: Although the orange welcome banner was removed this version is 
 still not supposed to be used in a productive environment!

 On this page, you'll find even more details:
 http://wiki.oxidforge.org/Downloads/4.6.0


 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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] eFire PayPal

2012-02-28 Thread Joscha Krug | marmalade.de
Hi guys,

i don't know, if this is the right place to ask but i don't know a
better one:

Could anyone explain to me, why the eFire Portlets are not available in
the eXchange?
It's so anoying! Each time we are in trouble with that, we had to write
emails, wait for the support to be online etc. pp.

Please guys - find a solution for that! You have the tools, you have the
code and you definitvely have not enough time to do the same things
again and again and again - like sending out modules via mail.

We just want to switch the PHP Version...

Best Joscha Krug

-- 

//-
 
marmalade.de
Joscha Krug
 
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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] oxchkversion

2012-02-27 Thread Joscha Krug | marmalade.de
Hi everybody,

is it possible, that oxchkversion.php is not longer maintained? Did i
miss something?

*These error(s) occured*

  * OXID eShop 4.5.6 in Revision 40808 does not exist.

Could anybody verify that?

Best Joscha
-- 

//-
 
marmalade.de
Joscha Krug
 
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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] oxchkversion

2012-02-27 Thread Joscha Krug | marmalade.de
Hi,

yes and after that i wanted to check if everything is still ok.
But it seems that i can't get a connection to the server.
Maybe it's like André said: Server down or not available for a moment.
Let's check again later.


//-
 
marmalade.de
Joscha Krug
 
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

Am 27.02.2012 16:03, schrieb Raimund Lang:

 did you upload the new pkg.rev with the last update you made?

  

 

 Haller Stahlwaren GmbH
 Am Gartennest 1
 74544 Michelbach/Bilz
 ---
 Tel.: 0791/47003
 Fax : 0791/47005
 www.haller-stahlwaren.de
 ---
 Sitz: Schwäbisch Hall
 Registergericht: Stuttgart HRB 570131
 Geschäftsführer: Hermann Hebsacker, Karin Hebsacker


 

 *Von:*dev-general-boun...@lists.oxidforge.org
 [mailto:dev-general-boun...@lists.oxidforge.org] *Im Auftrag von
 *Joscha Krug | marmalade.de
 *Gesendet:* Montag, 27. Februar 2012 15:54
 *An:* dev-general@lists.oxidforge.org
 *Betreff:* [oxid-dev-general] oxchkversion

  

 Hi everybody,

 is it possible, that oxchkversion.php is not longer maintained? Did i
 miss something?

 *These error(s) occured*

   * OXID eShop 4.5.6 in Revision 40808 does not exist.

 Could anybody verify that?

 Best Joscha

 -- 


 //-

  

 marmalade.de
 Joscha Krug

  

 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



 ___
 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

Re: [oxid-dev-general] oxchkversion

2012-02-27 Thread Joscha Krug | marmalade.de
Hi Michael,

that's why i don't bet! ;-)

Thank you very much!

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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

Am 27.02.2012 16:38, schrieb Michael Keiluweit:

 Hi,

  

 the service is available and still works.

 Please check the content of the column: OXEDITION in the table
 oxshops. I bet it's empty J

  

 Mit freundlichen Grüßen aus Freiburg,

  

 Michael Keiluweit

 Technical Support

  

 Fax +49 761 36889-29

 www.oxid-esales.com

   

  

 OXID eSales AG

 Bertoldstraße 48

 79098 Freiburg

 Deutschland

  

 Vorstand: Roland Fesenmayr (Vorsitzender), Andrea Seeger

 Vorsitzender des Aufsichtsrats: Harald Fuchs, Sitz: Freiburg

 Amtsgericht Freiburg i. Br., HRB 701648, USt-IdNr.: DE231450866

 __

  

  

  

  

 *Von:*dev-general-boun...@lists.oxidforge.org
 [mailto:dev-general-boun...@lists.oxidforge.org] *Im Auftrag von
 *Joscha Krug | marmalade.de
 *Gesendet:* Montag, 27. Februar 2012 16:08
 *An:* dev-general@lists.oxidforge.org
 *Betreff:* Re: [oxid-dev-general] oxchkversion

  

 Hi,

 yes and after that i wanted to check if everything is still ok.
 But it seems that i can't get a connection to the server.
 Maybe it's like André said: Server down or not available for a moment.
 Let's check again later.


 //-

  

 marmalade.de
 Joscha Krug

  

 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


 Am 27.02.2012 16:03, schrieb Raimund Lang:

 did you upload the new pkg.rev with the last update you made?

  

 

 Haller Stahlwaren GmbH
 Am Gartennest 1
 74544 Michelbach/Bilz
 ---
 Tel.: 0791/47003
 Fax : 0791/47005
 www.haller-stahlwaren.de http://www.haller-stahlwaren.de
 ---
 Sitz: Schwäbisch Hall
 Registergericht: Stuttgart HRB 570131
 Geschäftsführer: Hermann Hebsacker, Karin Hebsacker



 

 *Von:*dev-general-boun...@lists.oxidforge.org
 mailto:dev-general-boun...@lists.oxidforge.org
 [mailto:dev-general-boun...@lists.oxidforge.org] *Im Auftrag von
 *Joscha Krug | marmalade.de
 *Gesendet:* Montag, 27. Februar 2012 15:54
 *An:* dev-general@lists.oxidforge.org
 mailto:dev-general@lists.oxidforge.org
 *Betreff:* [oxid-dev-general] oxchkversion

  

 Hi everybody,

 is it possible, that oxchkversion.php is not longer maintained? Did i
 miss something?

 *These error(s) occured*

   * OXID eShop 4.5.6 in Revision 40808 does not exist.

 Could anybody verify that?

 Best Joscha

 -- 


 //-

  

 marmalade.de
 Joscha Krug

  

 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




 ___
 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

[oxid-dev-general] Hints for updating to 4.5.x

2011-09-21 Thread Joscha Krug | marmalade.de
Hi everybody,

just to save you some time (maybe) a short hint from our side:

If you're updating older shops to version 4.5.x the collation of
oxconfig and/or oxconfigdisplay might be wrong so no joins are possible.
No values in the backend are shown, escpecially on tab 2 and 3 of the
basic settings.

See Bug entry with solution: https://bugs.oxid-esales.com/view.php?id=3260

Best Joscha

//-
 
marmalade.de
Joscha Krug
 
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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Category thumbnail will be multilingual

2011-03-31 Thread Joscha Krug | marmalade.de
Hi,

it seems a bit random to me.

I expects, that the New Layout has language-specific text in those
images. Right?

So every user is from now on forced to upload one image twice or two
images, because the new default layout has text in the images? If this
is the background, please find another way!

Best

Joscha Krug

//-
 
marmalade.de
Joscha Krug
 
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


Am 30.03.2011 17:17, schrieb Vilma Liorensaityte:

 Hi,

 The thumbnail picture of category will be multilingual for Version 4.5.0.
 For this we added multilingual fields oxthumb_1, oxthumb_2 and
 oxthumb_3 in
 oxcategory table.

 What will change:
 1) For new shop install: if you want to show category picture in top of
 selected category list, you will have to assign this picture for all
 languages.
 2) For shops, who will update to 4.5.0: your assigned thumbnail will be
 automatically updated to all languages when you'll run UpdateApp. So,
 nothing changes for you.

 Regards
 Vilma


 ___
 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

Re: [oxid-dev-general] Changes in Order confirmation email

2010-10-13 Thread Joscha Krug / marmalade.de

Hi,

i have seen that and at the first sight it looks wrong.

But, if that will be changed, all e-mails in the inbox will have the 
same sender, so you are not longer able to filter via from.


If you, as most of the small CE-users may do, just work with e-mail, you 
are able to select very easy all e-mails relating to that customer at 
the moment. No matter if this is a question, an order or anything else.


This change will bring them some problems.

Best regards

Joscha Krug

//-
marmalade.de
Joscha Krug
www.marmalade.de http://www.marmalade.de/
k...@marmalade.de mailto:k...@marmalade.de
Gellertstr. 5
39108 Magdeburg
GERMANY
phone: +49 (0) 391 / 559 050 77
fax:  +49 (0) 391 / 559 050 79

Am 12.10.2010 17:21, schrieb Dainius Bigelis:

Hi,

FYI.
We got report about inconvenient structure of Order confirmation emails:
https://bugs.oxid-esales.com/view.php?id=1964

This will be fixed in some future releases.
Please note this, if you have some email filters setup, or similar stuff.

Best regards,
Dainius Bigelis
___
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