Re: [oxid-dev-general] V4.6 feature-request: module-handling

Tue, 24 Jan 2012 03:26:48 -0800

If you need suggestions, why not have an upload field for the module that accepts a .zip file with some kind of setup.php that
executes all the needed (extra) steps to install the module?
--

mit freundlichen Grüßen
Alexander Kludt


__________________________
Phone: 09283-5925453
Fax: 09283-592671
Skype: kingschnulli
Email: [email protected]
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 für den Empfänger () bestimmt, sollten
Sie nicht der Empfänger sein löschen Sie diese Nachricht
umgehend und geben Sie uns bitte per Email ([email protected]) Bescheid
über den fälschlichen Erhalt.




Rimvydas Paskevicius
24. Januar 2012 12:14

Hi,
 
This problem was also known, so we will find some solution to handle modules in subdirectories. Btw it very nice to hear some suggestion about modules handling, so if anyone has some good ideas, please share them to all, so we will make life easier to you Smile
 
 
 
Rimvydas Paskevicius
Developer

[email protected]
Phone +370 37 333053
Fax +370 37 333054
www.oxid-esales.com
 
Sent: Tuesday, January 24, 2012 11:45 AM
Subject: Re: [oxid-dev-general] V4.6 feature-request: module-handling
 
Hi,

just to mention it here again:

As many other agencies do, we also separate our modules in a subdirectory so you have

marm/module/module_class.php

at the moment , this is not possible with the new handling.

Would be great if you could find a solution for that.

Joscha
Am 24.01.2012 09:11, schrieb Rimvydas Paskevicius:

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Joscha Krug | marmalade.de
24. Januar 2012 10:45

Hi,

just to mention it here again:

As many other agencies do, we also separate our modules in a subdirectory so you have

marm/module/module_class.php

at the moment , this is not possible with the new handling.

Would be great if you could find a solution for that.

Joscha
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Rimvydas Paskevicius
24. Januar 2012 09:11

Hello,
 
Thanks to your suggestions . We are currently working on all stuff needed for automatic modules installing/uninstalling and activating/deactivating in one click. And your suggestions already are part of our work.
 
 
 
Rimvydas Paskevicius
Developer

[email protected]
Phone +370 37 333053
Fax +370 37 333054
www.oxid-esales.com
 
 
 
Sent: Friday, January 20, 2012 6:56 PM
Subject: [oxid-dev-general] V4.6 feature-request: module-handling
 

Hi,

while playing around with the new extension-features in v4.6 I’d like to propose following enhancements in oxmodule’s (de-)activation handling (already love the modulechain-handling):

·         Also add template-block extensions into the metadata for an easy (un-)install.

·         Parse menu.xml files (admin-tabs) only in activated modules’ directories.

·         Add a list of supported shop-versions into the module-metadata for a compatibility-check, which will either show a warning or even deactivate the module.

 

Best,

Manuel

 

[email protected] | www.mediaopt.de

 

derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen

 

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Manuel Reiß
20. Januar 2012 17:56

Hi,

while playing around with the new extension-features in v4.6 I’d like to propose following enhancements in oxmodule’s (de-)activation handling (already love the modulechain-handling):

·         Also add template-block extensions into the metadata for an easy (un-)install.

·         Parse menu.xml files (admin-tabs) only in activated modules’ directories.

·         Add a list of supported shop-versions into the module-metadata for a compatibility-check, which will either show a warning or even deactivate the module.

 

Best,

Manuel

 

[email protected] | www.mediaopt.de

 

derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen

 

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Reply via email to