Re: V6 to big metapackages, what about suggests?

[Tobias Merkl]

+1

Von: Jens Trant 
Datum: Mittwoch, 11. April 2018 um 11:58
An: "dev-general@lists.oxidforge.org" 
Betreff: V6 to big metapackages, what about suggests?

Hi all,

why do the meta-packages require a lot of optional stuff e.g. (demodata, 
amazon-pay-sdk, amazonpay4oxid, payone, …)?

From a perspective of an EE user, it is not really handy to build a custom 
composer.json with all the OXID components along the whole hierarchy and 
dependencies (metapackage-ee -> metapackage-pe -> metapackage-ce) and keep them 
up to date with every new release, for just moving out the stuff which will 
never be used, like the assets in the out directory from the demo-data packages.

I would really appreciate if the meta-packages from OXID could be clean 
packages and all the other optional stuff will be moved to the suggested 
section in the composer.json (https://getcomposer.org/doc/04-schema.md#suggest) 
because they are also not required in this term for a runnable OXID eShop. The 
user is then informed which packages could be installed optionally and can 
decide to require these (demodata, amazon-pay-sdk, amazonpay4oxid, payone, …) 
or not.

Example composer output could then be:
oxid-esales/oxideshop-metapackage-ce suggests installing 
oxid-esales/oxideshop-demodata-ce (OXID eShop demo data for the CE edition)

What do you think?

Thanks,
Jens-Christopher Trant


[losed]


Closed GmbH  |  Straßenbahnring 6  |  20251 Hamburg  |  Germany
T +49 40 441840 865  |  M +49 151 28439981  |  E 
jens.tr...@closed.com
closed.com  |  
facebook.com/closed 
  |  instagram.com/closedofficial 


Amtsgericht Hamburg HRB 53868 | Umsatzsteuer-Ident.-Nr.: DE 164980577
GF: Gordon Giers, Til Nadler, Hans Redlefsen

errors / exception interface

[Tobias Merkl]

Hey guys,



we have some trouble with exceptions ...



I created a pull request: https://github.com/OXID-eSales/oxideshop_ce/pull/609



Please have a look, what´s your opinion?

Regards

Tobias

---
Proud Sourcing GmbH, Kurpfalzstr. 14, 55218 Ingelheim
Tel: +49 (0) 6132 / 73 58 14 80, eMail: 
me...@proudsourcing.de

http://www.proudsourcing.de
http://www.proudcommerce.com

http://facebook.com/proudsourcing
http://plus.google.com/+ProudSourcingIngelheim

Re: [oxid-dev-general] Backend Order creation?

[Tobias Merkl]

or this one ;-)

https://github.com/proudcommerce/oxidjson


Von: , Ashant mailto:ash...@euroblaze.de>>
Antworten an: 
"dev-general@lists.oxidforge.org" 
mailto:dev-general@lists.oxidforge.org>>
Datum: Samstag, 5. September 2015 08:19
An: "dev-general@lists.oxidforge.org" 
mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] Backend Order creation?


Peter,

A webservice would be what you need.

If you are EE/PE, the good old SOAP Connector should be helpful.

If you are on CE, just search for "oxid soap web service".

Regards,
Ashant

Am 04.09.2015 13:04 schrieb "Peter Wiedeking" 
mailto:pe...@wiedeking.net>>:
Hi everyone,

I think about integrating my oxid shop into a kind of online marketplace.
Now we discuss, how the orders from the marketplace can be imported into my 
oxid shop.

Is there a module for backend order creation? I was thinking about a batch 
processing of an xml file or so.

I do not like to give them DB Access, so that they can create an order by 
themselves directly in the db. this will not work, i think.

Thanx in advance.

peter
___
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] Backend Order creation?

[Tobias Merkl]

hi peter,

there are some modules for backen order integration bei admin gui, but i
don´t think with an batch job.

regards

Tobias


-Ursprüngliche Nachricht-
Von: Peter Wiedeking 
Antworten an: "dev-general@lists.oxidforge.org"

Datum: Freitag, 4. September 2015 13:02
An: "dev-general@lists.oxidforge.org" 
Betreff: [oxid-dev-general]  Backend Order creation?

Hi everyone,

I think about integrating my oxid shop into a kind of online marketplace.
Now we discuss, how the orders from the marketplace can be imported into
my oxid shop.

Is there a module for backend order creation? I was thinking about a
batch processing of an xml file or so.

I do not like to give them DB Access, so that they can create an order
by themselves directly in the db. this will not work, i think.

Thanx in advance.

peter
___
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] CMS with image upload function

[Tobias Merkl]

http://marat.ws/bla-rfm/ ;-)

Regards

Tobias

Am 25.02.15 14:12 schrieb "Hans Jürgen Fricke" unter :

>
>  
>  
>You need to aktivate the plugin:
>
>jbimages => plugins/jbimages/plugin.js
>
>in the Plugin-field.
>
>
>
>-- 
>  Beste Grüße
>  Hans Jürgen Fricke
>  
>  
>  
>  Hermann-Enters-Str. 1
>  42287 Wuppertal
>  
>  Fon 0172 4217539
>  
>  email: h...@narendra.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] CMS with image upload function

[Tobias Merkl]

http://marat.ws/bla-tinymce/

Regards

Tobias


Am 25.02.15 13:04 schrieb "Mirza Ahtasham Ahmad" unter
:

>Hi,
>
>Is there any open source module for Oxid CE for Richtext Editor in CMS
>with image upload functionality?
>
>
>
>Mit freundlichen Grüßen | Warm Regards,
>Mirza Ahmad
>M +4917645387460 | Skype: ahtasham82
>
>
>
>
>
>
>
>
>
>___
>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] action widget

[Tobias Merkl]

Hey guys,

How can i use an action widget, e. h. to display all topseller or new products 
in sidebar, without a module?

It was not possible, so i created a PR: 
https://github.com/OXID-eSales/oxideshop_ce/pull/37
But this PR was rejected allegedly because the function is integrated since 
oxid 4.9.

Regards

Tobias


---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim

Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de

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

Re: [oxid-dev-general] Next user group meetings: Berlin, NRW (Essen) and Leipzig

[Tobias Merkl]

yes, outlook Š.

a shorten link: http://goo.gl/77UlXz

Viele Grüße

Tobias Merkl
Senior Software Engineer


---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim

Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de







-Ursprüngliche Nachricht-
Von: Maximilian Berghoff 
Antworten an: "dev-general@lists.oxidforge.org"

Datum: Montag, 12. Januar 2015 14:02
An: "dev-general@lists.oxidforge.org" 
Betreff: Re: [oxid-dev-general] Next user group meetings: Berlin, NRW
(Essen) and Leipzig

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The links seems to be broken.

greets max

Am 12.01.2015 um 13:58 schrieb Tobias Merkl:
> Hi guys,
> 
> little update ;-)
> 
> next OXID UG Meeting Nuremberg on 28/01/15.
> 
> 
>https://openspacer.org/12-oxid-usergroup-nuernberg/59-treffen-28-januar-20
>1
>
> 
5/
> 
> 
> Viele Grüße
> 
> Tobias Merkl Senior Software Engineer
> 
> 
> --- Proud Sourcing GmbH Kurpfalzstr. 14 55218 Ingelheim
> 
> Tel: +49 (0) 6132 / 73 58 14 80 eMail: me...@proudsourcing.de
> 
> 
> 
> 
> 
> 
> 
> -Ursprüngliche Nachricht- Von: Marco Steinhaeuser
>  Antworten an:
> "dev-general@lists.oxidforge.org"
>  Datum: Donnerstag, 8. Januar 2015
> 15:41 An: "dev-general@lists.oxidforge.org"
>  Betreff: [oxid-dev-general] Next
> user group meetings: Berlin,  NRW (Essen) and Leipzig
> 
> Hi folks,
> 
> I'm glad to announce the next user group meetings in - Berlin:
> 
>http://www.oxid-ug.de/events/oxid-usergroup-berlin-schnittstellen-zu-blogs
>-
>
> 
und-cms/
> - NRW (Essen): 
> 
>http://www.oxid-ug.de/events/oxid-usergroup-nrw-get-together-planung-2015/
>
> 
- - and the very first one in Leipzig for all you guys in and around
Saxony,
> Saxony Anhalt and Thuringia. We are still about to find an
> appropriate date for it: http://doodle.com/nmx8di4iheyr42bd
> 
> Looking forward! 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
> 

- -- 

- --
Maximilian Berghoff Mayflower GmbH
Gneisenaustraße 10/11   Tel.: +49 931 359 65 1180
D-97074 WürzburgFax : +49 931 359 65 28
maximilian.bergh...@mayflower.de   http://www.mayflower.de

Mayflower GmbH: http://mayflower.de/impressum
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBAgAGBQJUs8XhAAoJEHNImtue0q8gEmIP/0226Y7+4WuggefI7l9EWHfk
lKTQ4wnOXyupd3sKlwToNBF3f1eREJQCU7Jn+kDTrd29OHgI2DLGnLzlpuHx+kFc
P/IX7QGHE5G0jntyX+4pup4Sc16IyTp3TcBasEKBY7TqkyxCZcdJrYo5IeL4ybZJ
VoPvqiUTlLvE+zZm9P4G/gev183x0+fNevXEXNKdikJNsg+EbIODGB37InK4LSqE
8vGC4wvHRGkWqyMOZ7fl9TdfRbh4Dq7+G4guGvE2iubLWOVJ+B/fg/ur2kRJ1ibZ
V7Vy1TlSskJAltc/1oAGhdlFKpbMf+LkSXMpcLaCxtrI6ZbxvI7PsMWe9SR57KdX
1nSfEr3eExRnG/Hq9iHQ65/EgN9lT1Xr3ws0D6XkfuOCAH+HVrNC95zhvq6ZeoT4
iSBuKmRqCz136KNpCAtpJyA4J+bQjzE7L4ZYIyT2PvxoHEXhYGf7xkyH49VX5dT6
s8dYS34JCYuPz4UMlAgDoZegENr/pg7HE6B/a2Hh+6t5XTCeudO9ghabLfAhr9Uk
p9iLh7s8U8bBqwpLsHktOCjCbWw/nmixt+8aL1qe1coIC0pEuLVokBBoltEM5dnG
hCFlK7x0PVKNBTqEolU1GoYJfmLyBAE9sGOTTutVNxFpn96IegZj2KnYc5pUE7nl
a30GNzGxgb0fpYq7ba9q
=uOR8
-END PGP SIGNATURE-
___
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] Next user group meetings: Berlin, NRW (Essen) and Leipzig

[Tobias Merkl]

Hi guys,

little update ;-)

next OXID UG Meeting Nuremberg on 28/01/15.

https://openspacer.org/12-oxid-usergroup-nuernberg/59-treffen-28-januar-201
5/


Viele Grüße

Tobias Merkl
Senior Software Engineer


---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim

Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de







-Ursprüngliche Nachricht-
Von: Marco Steinhaeuser 
Antworten an: "dev-general@lists.oxidforge.org"

Datum: Donnerstag, 8. Januar 2015 15:41
An: "dev-general@lists.oxidforge.org" 
Betreff: [oxid-dev-general] Next user group meetings: Berlin,   NRW (Essen)
and Leipzig

Hi folks,

I'm glad to announce the next user group meetings in
- Berlin: 
http://www.oxid-ug.de/events/oxid-usergroup-berlin-schnittstellen-zu-blogs-
und-cms/
- NRW (Essen): 
http://www.oxid-ug.de/events/oxid-usergroup-nrw-get-together-planung-2015/
- and the very first one in Leipzig for all you guys in and around Saxony,
Saxony Anhalt and Thuringia. We are still about to find an appropriate
date for it: http://doodle.com/nmx8di4iheyr42bd

Looking forward!
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] ioly OXID Connector

[Tobias Merkl]

Hey guys,

Together with „gn2 netwerk“ and „rent a hero“ we build an new module installer 
called „ioly“.

https://github.com/ioly/ioly


ioly is a decentralized/centralized universal package installer for web based 
php software. You can use it with any system that supports 
modules/extensions/packages. e.g. OXID eSales, Wordpress, Redaxo etc. etc. 
etc..The ioly system is driven by a "cookbook", stored on GitHub, which 
contains "recipes" to install any zip-based package. If something is missing, 
you can send us a pull request to extend/improve the main ioly cookbook. As 
soon as we merge your modifications, EVERY ioly installation has access to your 
package!

We also build a ioly OXID connector, so it´s f*** easy to install new modules 
in oxid ;-)

download: https://github.com/ioly/ioly/tree/connector-oxid
video: https://www.youtube.com/embed/8JnDZxhWETo?vq=hd720

Search for oxid ioly modules: http://getioly.com

Regards

Tobias Merkl
Senior Software Engineer


---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim

Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de<mailto:me...@proudsourcing.de>

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

Re: [oxid-dev-general] OXID eShop Release Candidate (RC) 4.9 available

[Tobias Merkl]

Hi alex,

I think this is one of the discussions regarding a lot of features ;-)

But feel free to contribute this contribution ;-)

Regards

Tobias


Von: Alexander Kludt mailto:cod...@aggrosoft.de>>
Antworten an: 
mailto:dev-general@lists.oxidforge.org>>
Datum: Thu, 18 Sep 2014 14:47:25 +0200
An: mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] OXID eShop Release Candidate (RC) 4.9 available

Hi there,

Tracking URL should be per Delivery and not a global setting,
I know at least 10 shops that have multiple carriers.
What do you think?
[cid:part1.08070405.09040207@aggrosoft.de]
Marco Steinhaeuser
Donnerstag, 18. September 2014 12:08
Hi folks,

There's a RC for OXID eShop version 4.9 available for download:
http://exchange.oxid-esales.com/OXID-oxid-oxid/OXID-eShop/OXID-eShop-CE-Release-Candidate-4-9-0-4-9-0-RC1-Beta-CE-4-8-x.html

As always, you'll find the main changes documented in the release notes at 
OXIDforge. Please note that this page is still not finished, other information 
might appear there until the final release.
http://wiki.oxidforge.org/Downloads/4.9.0_5.2.0

Would be glad to see your feedback.

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

--
mit freundlichen Grüßen
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 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 
(cod...@aggrosoft.de) Bescheid
über den fälschlichen Erhalt.

___ 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] 2nd OXID Usergroup Meeting Nuremberg

[Tobias Merkl]

Hey guys,

this wednesday is the 2nd OXID usergroup meeting nuremberg.

http://www.oxid-ug.de/events/zweites-treffen-der-oxid-usergroup-nuernberg/

Kindest regards

Tobias Merkl
Senior Software Engineer


---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim

Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de<mailto:me...@proudsourcing.de>

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

[oxid-dev-general] First DevOps-Camp in Germany

[Tobias Merkl]

Hi guys,

I think we all are DevOps, or not? ;-) So i would like to invite you
within this mail.

My college Stefan and me are hosting the first DevOps-Camp in Germany from
March 28. to 30. In Nuremberg.

Perhaps it´s interesting for you and you would like to join us?

Visit: www.devops-camp.de

Kindest regards
  
Tobias Merkl
Senior Software Engineer
  
  
---
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim
  
Tel: +49 (0) 6132 / 73 58 14 80
eMail: me...@proudsourcing.de








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

Re: [oxid-dev-general] New feature for delivery tracking

[Tobias Merkl]

So guys, feel free to extend and push ;-)

Regards

Tobias



Am 10.03.14 21:59 schrieb "Joachim Barthel" unter :

>Hi,
>yes I would appreciate a more flexible solution too. As I mentioned some
>time ago (10-2012 -> http://forum.oxid-esales.com/showthread.php?t=12866
>), there are several reason why not only one supplier is used.
>
>
>Joachim
>
>Joachim Barthel-
>OxAds 
>table-CE-4-3-x-4-7-x.html> -- OxProbs
>-4-Stable-CE-4-3-x-4-7-x.html> -- Piwik-Plugin
>er-Piwik-0-10-Stable-CE-4-3-x-4-7-x.html> -- jxAttrEdit
>ttrEdit-0-2-Stable-CE-4-7-x.html> -- jxExcptns
>-0-1-1-Stable-CE-4-7-x.html> -- jxSales
>les-0-2-Stable-CE-4-7-x.html>
>
>
>
>
>2014-03-10 16:47 GMT+01:00 Alexander Kludt :
>
>Hi there,
>
>this url should be per delivery and not  global settings,
>there are a lot of shops using more than one delivery service.
>-- 
>mit
> freundlichen Grüßen
>
>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 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 (cod...@aggrosoft.de)
> Bescheid
>
>über den fälschlichen Erhalt.
>  
>
>
>
>
>
>   
>   
>
>   Vilma Liorensaityte 
>   
>   
>  Montag, 10. März
>2014 16:43
>
>
>  Hi
> everybody,
>
>we decided to add a new feature, related to bug #2164, to the dev-branch
> - to be published with the next major version.
>
>This feature was contributed by @tabls (Proudsourcing, thanks a lot!)
>with the pull request #94:
>https://github.com/OXID-eSales/oxideshop_ce/pull/94
>
>The before hard coded URL for the delivery tracking can now be
>configured in the admin panel, no need for writing a module any more:
>Master settings->Core Settings->Settings->Other
>Settings->Parcel service tracking URL.
>
>When the delivery tracking code is set, tracking appears close to the
>order: Administer Orders->Orders->Main->Tracking Link
>
>Cheers!
>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] Pros and cons for module-connectors

[Tobias Merkl]

but what are these reusable extensions?

oxid is on the may, makeing shop core slender. so atm it´s very hard to
put new code into :-(

the most used „helper module“ is clear temp. there is an good extension
from oxid cookbook,
or „moduledebug“ or „devmodules“ from oxid core developers.
another good helper module would be a logger.

perhaps we can make here an collection of modules which we need or use and
post it to
oxidforge wiki?

regards

tobias


-Ursprüngliche Nachricht-
Von: Roman Allenstein 
Organisation: Spark 5
Antworten an: "dev-general@lists.oxidforge.org"

Datum: Dienstag, 21. Januar 2014 09:50
An: "dev-general@lists.oxidforge.org" 
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors

I really don't like the use of an connector but some of my team-member
argument that it's good to put all reusable extensions in one
connector-module instead of putting them in every module, that we are
developing.
My argument against a connector is the problem with the dependencies
while an upgrade-process of the connector.

@Joscha
the use of composer is a really great idea. Have you allready used
composer for a module?

@OXID
I agree to Joscha, that we need a dependency-setting (including version)
for modules.

Greets
Roman

 > Am 21.01.2014 09:40, schrieb Tobias Merkl:
> roman, what´s your reason why you would use/create an own connector?
>
> Von: 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
> 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
>>
>> 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

Re: [oxid-dev-general] Pros and cons for module-connectors

[Tobias Merkl]

roman, what´s your reason why you would use/create an own connector?

Von: Joscha Krug | marmalade GmbH mailto:k...@marmalade.de>>
Antworten an: 
"dev-general@lists.oxidforge.org" 
mailto:dev-general@lists.oxidforge.org>>
Datum: Dienstag, 21. Januar 2014 09:38
An: "dev-general@lists.oxidforge.org" 
mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors

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
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
Das einfach geniale OXID eShop Modul.
Ab sofort in unserem 
Online-Shop
 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

[http://static.aikme.de/mail/sig.jpg]

aikme GmbH
Rheinstraße 43-45
55116 Mainz / Deutschland
Telefon: 06131 92 06 503
Telefax: 06131 92 08 334
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
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
http://dir.gmane.org/gmane.comp.php.oxid.general




___
dev-general mailing list
dev-general@lists.oxidforge.orghttp://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] Best practices on OXID and git

[Tobias Merkl]

hey guys,

if you use this GIT repo (e. g. with different branches dev/stage/master) for 
deployment on all systems, you have to commit all files.
but some should be ignored: like /tmp, /log, /export and all config-files.

you can make automatic or manual commits on e. g. live system (article images 
or something other live content).

kindest regards

tobias



Von: dev-general-boun...@lists.oxidforge.org 
[dev-general-boun...@lists.oxidforge.org] im Auftrag von Althoff, Danny 
[danny.alth...@edicos.de]
Gesendet: Dienstag, 17. September 2013 17:35
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Best practices on OXID and git

Hi Roman, hi Madonius

you forgot to mention that you can have your own smarty-plugins inside the 
"core/smarty/plugins"-folder. Having a custom loader is another topic too ;)

Having a whitelist can be a solution, but may be not the best (imagine the 
situation you forgot "that one" location and you will start wondering, why you 
system breaks).

greets
Danny

-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Roman Allenstein
Gesendet: Dienstag, 17. September 2013 16:00
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Best practices on OXID and git

Hi Madonius,
i think you should ignore everything except the following directories:

- modules
- out/your_theme

because you should not change anything inside the core.

I would suggest you to create a checkout for every module and every theme you 
are working on. Do not commit the OXID-scripts to your repository to prevent 
changing the core-scripts.


Greets
Roman

Am 17.09.2013 15:48, schrieb Madonius:
> Dear fellow devs,
>
>I am developing for our new oxid webshop and I am using git.
> Everything works fine as it is a repository just for me. But now other
> developers are to be included in the proces, are there common recipies
> on terms of .gitignore, comitting policy etc.?
> What are your experiences/methods proven most sucessfull?
>
> Besides what editors would you recommend for windows, which are fit
> for not so versatile users?
>
> Greets,
>Madonius
> ___
> dev-general mailing list
> dev-general@lists.oxidforge.org
> http://dir.gmane.org/gmane.comp.php.oxid.general


--
Dipl.Winf. (FH) Roman Allenstein
Software-Developer
Spark 5 GmbH
Rheinstraße 97
64295 Darmstadt

Fon: +49-6151-8508-048
Fax: +49-6151-8508-111

Mail: 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
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] OXCOUNTERS

[Tobias Merkl]

hey ray,

> Yes, exactly – I´m talking about the counters which are stored into table 
> oxcounters. I know about the order number, I know as well, that oxuser does 
> not use oxcounter.
> Therefore I wanted to know, if there is an overview about which counters make 
> use of this function – and which not.
only oxordernr is used in oxcounters.
no invoicenr, no customernr, …
y? please asked oxid ;-) 

> By the way, while seeking through the database I found ‘oxbillnr’ AND 
> ‘oxinvoicenr’ within table oxorder – what is the difference?
on is the order number, and one the invoice number on pdf ;-) 

regards

Tobias Merkl
Senior Software Engineer

-- 
Proud Sourcing GmbH
Kurpfalzstr. 14
55218 Ingelheim
Tel.: +49 (0)6132 4308830
info@proudsourcing,de
Handelsregister: Mainz, HRB 43170

Geschäftsführung: Stefan Peter Roos, Alexander Talmon



Am 30.04.2013 um 10:42 schrieb Haller Stahlwaren GmbH - Raimund Lang 
:

> Hi Anatolij
>  
> Yes, exactly – I´m talking about the counters which are stored into table 
> oxcounters. I know about the order number, I know as well, that oxuser does 
> not use oxcounter.
> Therefore I wanted to know, if there is an overview about which counters make 
> use of this function – and which not.
>  
> By the way, while seeking through the database I found ‘oxbillnr’ AND 
> ‘oxinvoicenr’ within table oxorder – what is the difference?
>  
> Ray
>  
> Von: dev-general-boun...@lists.oxidforge.org 
> [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Anatolij 
> Woromsbecher
> Gesendet: Dienstag, 30. April 2013 10:36
> An: dev-general@lists.oxidforge.org
> Betreff: Re: [oxid-dev-general] OXCOUNTERS
>  
> Hi,
> 
> when you mean the oxcounter table, I think its the counter for 
> OXORDER__OXORDERNR
> 
> Mit Freundlichen Grüßen
>  
> Anatolij Woromsbecher
> Inhaber
>  
> eCom Software Solution 
> Inh. Anatolij Woromsbecher
> Nickelstr. 21
> 33378 Rheda-Wiedenbrück
>  
> Tel:+49 5242 58 199 80 
> Fax:+49 5242 58 199 81
>  
> E-Mail: a...@ecom-software.de
> Web:www.ecom-software.de
>  
> Wir bieten E-Commerce Software nach Maß
>  
> Am 30.04.2013 10:19, schrieb Haller Stahlwaren GmbH - Raimund Lang:
> Hi devs!
>  
> Is there an overview anywhere, which counters are controlled by oxcounter? 
> Apparently oxbillnr not.
>  
> Ray
>  
> ___
> 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] function names 5.0/4.7

[Tobias Merkl]

hellas,

does anyone knows an useful reason, why some functions in 4.7/5.0 have been 
renamed like

oxSession

getVar() --> getVariable() 

regards

Tobias Merkl
Softwareentwicklung


***
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
eMail: me...@shoptimax.de 
Web: www.shoptimax.de
Blog: www.shoptimax.de/blog/
***






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

[oxid-dev-general] templatehandling in modules

[Tobias Merkl]

hey guys,

one question to our core developer ;-)

what was your idea, to manage module templates for 4.6.x and older versions 
like 4.4.x and 4.5.x with on file package.

it´s very wasteful to keep several file structures for each version e. g.

4.6.x
=
/modules/mymodule/out/tpl/...

< 4.6
=
/out/azure/mymodule/...


i would like to use the new file structure (4.6) for all module/shop versions!

kindest regards

Tobias Merkl
Softwareentwicklung


***
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
eMail: me...@shoptimax.de 
Web: www.shoptimax.de
Blog: www.shoptimax.de/blog/
***





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

Re: [oxid-dev-general] Recent Viewed Products

[Tobias Merkl]

Hello guys,

the lastseen products are only saved into the session, when you use 
"$oView->getLastProducts() " in details, e. g.:

[{ assign var=something value=$oView->getLastProducts() }]


Example for smx_oxviewconfig.php:

---

class smx_oxviewconfig extends smx_oxviewconfig_parent
{
public function smxLastSeen()
{
$oHistoryArtList = oxNew( 'oxarticlelist' );
$oHistoryArtList->loadHistoryArticles( null );
return $oHistoryArtList;
    }
}

---

Kindest regards


Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Kai Gazmaga
Gesendet: Mittwoch, 20. Juni 2012 09:35
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Recent Viewed Products

Hi!

oxView and oxUbase can not be overloaded. You can use oxViewConfig instead. 
With this you should have access to the new functionality you integrate from 
every template.

Regards, Kai



VektorDesign - Online-Shops und Programmierung

Kai Gazmaga 
Katharinenstraße 57 
73 728 Esslingen

Tel.: +49 711 - 25516226 
Fax: +49 711 - 25518078

Mail: i...@vektordesign.de 
Web: www.vektordesign.de



Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Sai Chandra 
Sekhar Madala
Gesendet: Mittwoch, 20. Juni 2012 09:31
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Recent Viewed Products

Hi Mr.Marco & Mr.Frank,

@Thanks Mr.Marco.

@Frank .Thank you for the module.As you pointed out it is built in,but only for 
detail page.I have used your module and it works fine in detail page as well as 
start page but not through out the shop.I have extended the aList & start 
classes also I tried to extend oxView & oxUBase, but they do not seem to 
work.Please suggest me the class to extend so that it works through out the 
shop.

Thanks & Regards,
Sai Chandra Sekhar.M
On Tue, Jun 19, 2012 at 10:49 PM, Frank Zunderer  
wrote:
Hi,
 
Last seen products is already built in, but only for detail view. Here is a 
module that activates last seen in azure throughout the shop, just add the 
views where you want to show it in metadata.php:
http://forum.oxid-esales.com/showthread.php?t=708&page=5
 
Regards,
Frank
 
 
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Sai Chandra 
Sekhar Madala
Gesendet: Dienstag, 19. Juni 2012 16:52
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Recent Viewed Products
 
Dear All,

I have a requirement where I have to show the recent viewed products.I have 
tried to implement this through a module.

First I have stored the ox-id's of the viewed products inside a session 
variable and retrieved them and created an object and loaded the product using 
load function.

1) This is the code in details.php for storing session variable.
 
if(isset($_SESSION['views']))
$_SESSION['views']=$_SESSION['views'].",".$oProduct->oxarticles__oxid->value;
else
$_SESSION['views']=$oProduct->oxarticles__oxid->value;

2) Then I have used the below code in Module
public function getrecentviewproduct(){
        $i=0;
        if($procoxid = oxSession::getVar('views')){
            $sOxid =  explode("," , $procoxid);
            foreach($sOxid as $procid){            
                $oArt = oxNew('oxarticle');
                $oArt->load($procid);
                $oArtList[$i] = $oArt;
                $i++;
            }
            return $oArtList;
        }
        return null;
    }

This module when registered with start class works fine in start page,but our 
requirement is that it should work through out the shop.

Please suggest which class has to be extended so that the above will work 
through out the shop.


Thanks & Regards,
Sai Chandra Sekhar.M,
Devblaze Inc.

___
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] Modulehandling with Version 4.6

[Tobias Merkl]

Hey Joscha,

when you are deactivating an modul, this information will be stored in 
oxconfigparam "aDisabledModules".

It would be nice to have the new module debugging module from the oxid 
core-team ;-)

Kindest Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Joscha Krug | 
marmalade.de
Gesendet: Montag, 18. Juni 2012 16:36
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Modulehandling with Version 4.6

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

 '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
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] new module structure in 4.6 and admin include files not working?

[Tobias Merkl]

Great, thanks ;-)

Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alfonsas 
Cirtautas
Gesendet: Donnerstag, 31. Mai 2012 11:16
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] new module structure in 4.6 and admin include 
files not working?

HI,

thank you for quick response. We will do check inside oxajax.php to fall back 
to file include if oxNew will fail (and will remove it in next major version)

Alf


From: dev-general-boun...@lists.oxidforge.org 
[dev-general-boun...@lists.oxidforge.org] on behalf of Lang, Raimund 
[r.l...@haller-stahlwaren.de]
Sent: Thursday, May 31, 2012 12:05 PM
To: dev-general@lists.oxidforge.org
Subject: Re: [oxid-dev-general] new module structure in 4.6 and admin include 
files not working?

Good point...

Ando f course need to upload a new version to the eXchange as well.
Maybe a (temporary) workaround would be better, so modules do not need to 
changed again after just one minor release.

This big change can be implemented later anyway, in 4.7 or in 5.0 when even 
more changes are made.

Ray



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


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Tobias Merkl
Gesendet: Donnerstag, 31. Mai 2012 10:12
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] new module structure in 4.6 and admin include 
files not working?

Hey alf,

this sounds good, but ...

all module developer has to update their modules in 4.6.2 (?) if they are using 
admin ajax classes! :-(

Kindest Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alfonsas 
Cirtautas
Gesendet: Donnerstag, 31. Mai 2012 09:05
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] new module structure in 4.6 and admin include 
files not working?

Hi

With bugfix for https://bugs.oxid-esales.com/view.php?id=4037 we will move and 
rename all ajax list related admin classes. As an example 
admin/inc/actions_article.inc.php will become admin/actions_article_ajax.php

With this change it will be possible to extend existing and register new ajax 
list files in module metadata.

Alf.


From: dev-general-boun...@lists.oxidforge.org 
[dev-general-boun...@lists.oxidforge.org] on behalf of Stefan Moises 
[moi...@shoptimax.de]
Sent: Monday, May 14, 2012 12:22 PM
To: dev-general@lists.oxidforge.org
Subject: 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 oxaja

Re: [oxid-dev-general] new module structure in 4.6 and admin include files not working?

[Tobias Merkl]

Hey alf,

this sounds good, but ...

all module developer has to update their modules in 4.6.2 (?) if they are using 
admin ajax classes! :-(

Kindest Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alfonsas 
Cirtautas
Gesendet: Donnerstag, 31. Mai 2012 09:05
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] new module structure in 4.6 and admin include 
files not working?

Hi

With bugfix for https://bugs.oxid-esales.com/view.php?id=4037 we will move and 
rename all ajax list related admin classes. As an example 
admin/inc/actions_article.inc.php will become admin/actions_article_ajax.php

With this change it will be possible to extend existing and register new ajax 
list files in module metadata.

Alf.


From: dev-general-boun...@lists.oxidforge.org 
[dev-general-boun...@lists.oxidforge.org] on behalf of Stefan Moises 
[moi...@shoptimax.de]
Sent: Monday, May 14, 2012 12:22 PM
To: dev-general@lists.oxidforge.org
Subject: 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_

Re: [oxid-dev-general] Problem 4.5.6 oxubase

[Tobias Merkl]

Sorry guys, but now it´s an bug!

All developer has to check their moduls for oxid > 4.5.6 and make db-fieldnames 
UPPERCASE ?!

Kindest Regards

Tobias



-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Linas Kukulskis
Gesendet: Montag, 23. Januar 2012 15:59
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Problem 4.5.6 oxubase

Hi,

its related to this bug: https://bugs.oxid-esales.com/view.php?id=3463.


Linas Kukulskis
Developer

linas.kukuls...@oxid-esales.com
Phone +370 37 333053
Fax +370 37 333054
www.oxid-esales.com


OXID eSales AG
Bertoldstraße 48, 79098 Freiburg, Germany

Lithuanian Division
K. Petrausko g. 26-316, Kaunas LT-44158, Lithuania


Sales tax identification number: DE 231 450 866
Board of directors authorized to represent the company:
Roland Fesenmayr (chairman), Eric Jankowfsky, Andrea Seeger
Chairman of the supervisory board: Harald Fuchs
Head office Freiburg: Bertoldstraße 48, 79098 Freiburg, Germany
Court of registration: Amtsgericht Freiburg i. Br., HRB 701648, Office 
reference number: 06/447/41949



The next Generation of Premium eCommerce


Latest version OXID eShop 4 as open source



From: dev-general-boun...@lists.oxidforge.org 
[dev-general-boun...@lists.oxidforge.org] on behalf of Tobias Merkl 
[me...@shoptimax.de]
Sent: Monday, January 23, 2012 3:44 PM
To: dev-general@lists.oxidforge.org
Subject: [oxid-dev-general] Problem 4.5.6 oxubase

Hello guys,

after changes in oxubase.php eShop 4.5.6 we have problems with custom database 
fields.

All custom fields are no longer in the e. g. article object.

There is no entry in bugtracker / changelog, why?

Kindest Regards

Tobias



*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


___
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] Problem 4.5.6 oxubase

[Tobias Merkl]

Hello guys,

after changes in oxubase.php eShop 4.5.6 we have problems with custom database 
fields.

All custom fields are no longer in the e. g. article object.

There is no entry in bugtracker / changelog, why?

Kindest Regards

Tobias



*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


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

[oxid-dev-general] new session after logout/login

[Tobias Merkl]

Hello guys,

i'll like to extends default login() function from oxuser view.

In my own login() function i don't calling at the begining parent::login(...) 
but doing my nesseccesary stuff, like finding user in oxuser table and save in 
session user's name ( oxSession::setVar( 'usr', $this->oxuser__oxid->value ); ) 

But i also use 3-rd part script for connectiong with DB2. This script is need 
it for upgrade some information in DB2 database (it has been included in 
modules/functions.php).
In my own login() function (for upgrade DB2 database by my 3-rd part class) in 
need to get to old sessionID and new sessionID - cause after login sessionID is 
changing.

First 2 lines in login() looks like this:
- oxUtilsServer::getInstance()->getOxCookie(oxSession::getInstance()->getName()
- oxSession::getInstance()->getId()
both return me old sessionID

At the end of login() function (after success in finding user in db) i'm 
calling the same functions as before:
- oxUtilsServer::getInstance()->getOxCookie(oxSession::getInstance()->getName()
- oxSession::getInstance()->getId()
...and..i though that i should receive new seesionID, but hey no. 

The funny thing is that script doesn't see new sessionID, but browser cookie 
already has new seesionID :)
My questions is :
- when, for sure, new sessionID is generated?
- in which function (even in core files) is the place, where sessionID is 
geenrated?
- where is the place and logic for rewriting basket info (for non-login user) 
to basket of logged ins user (when you are not logged in you adding some 
articles to basket and you get some sessionID, after login you've got new 
sessionID and the same article in basket, so basket is beeing update also after 
login in) 
- how can i get to old sessionID and new sessionID in own login function?

Kindest regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*



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

[oxid-dev-general] oxseologs

[Tobias Merkl]

Hello guys,

if i see, oxseologs only logs some information about older seo-links, right?

Is this really necessary? Why cant´d I disable it?

In bigger shops we have oxseologs with several million entries, that's not good 
for performance.

Kindest regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*



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

Re: [oxid-dev-general] oxseo fullscan [T-6VJH77ICB7-35]

[Tobias Merkl]

count(*),avg(length(oxstdurl)),max(length(oxstdurl)),avg(length(oxseourl)),max(length(oxseourl))

44299,  67.3106,131,67.1233,269

44299


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von anzido GmbH
Gesendet: Donnerstag, 28. April 2011 09:16
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] oxseo fullscan [T-6VJH77ICB7-35]

And some from me:

Shop 1:

Field_name  Min_value   Max_value   Min_length  Max_length  
Empties_or_zerosNulls   Avg_value_or_avg_length Std 
Optimal_fieldtype
live_babymarkt.oxseo.OXSTDURL   
?cl=azsitemap&anid=c341929fd71d24d53e11f1fdf99c60a3 
index.php?cnid=oxmore&cl=alist  17  113 0   0   78.9497 
NULLVARCHAR(113) NOT NULL
live_babymarkt.oxseo.OXSEOURL   11/ 
xKinderwagen-Babytragen/Zwillingswagen-Geschwisterwagen/ABC-DESIGN-Tragewanne-zum-Zoom-Orange-black-Kollektion-2010.html
2   191 0   0   83.1851 NULLVARCHAR(191) 
NOT NULL

count(*)
287345


count(*)avg(length(oxstdurl))   max(length(oxstdurl))   
avg(length(oxseourl))   max(length(oxseourl))
287345  78.9497 113 83.1851 191


Shop 2:
---
Field_name  Min_value   Max_value   Min_length  Max_length  
Empties_or_zerosNulls   Avg_value_or_avg_length Std 
Optimal_fieldtype
usrdb_worhppxo2.oxseo.OXSTDURL  
/Zuckerwaren/Brausepulver-Bonbons/Ahoj-Brause/&...   
index.php?cnid=oxmore&cl=alist  17  172 0   0   89.4872 
NULLVARCHAR(172) NOT NULL
usrdb_worhppxo2.oxseo.OXSEOURL  1-Alles-fuer-die-Schultuete.html
Zuckerwaren/Zuckerwatte-im-Becher.html  2   135 0   0   53.6110 
NULLVARCHAR(135) NOT NULL


count(*)
66083


count(*)avg(length(oxstdurl))   max(length(oxstdurl))   
avg(length(oxseourl))   max(length(oxseourl))
66083   89.4873 172 53.6112 135




Beste Grüße aus Dortmund! 
Andreas Ziethen | Geschäftsführung 

-- 

anzido GmbH 
Kirchhörder Str. 12 
44229 Dortmund 
Tel.: 0231 - 60 71 079 
Fax.: 0231 - 60 71 081 
Mobil:0176 - 8325 1488 
Email: i...@anzido.com 
Web: http://www.anzido.com ( http://www.anzido.com/ ) 

USt-ID: DE257982972 
Geschäftsführung: Andreas Ziethen 
Amtsgericht Dortmund HRB 20883
-Ursprüngliche Daten-
Datum: 27.04.2011 13:06:27
Von: ŠarunasValaškevicius 
An: 
Betreff: Re: [oxid-dev-general] oxseo fullscan
Vorgang: T-6VJH77ICB7-35

> Hi,
> 
> we are currently fixing this issue,
> https://bugs.oxid-esales.com/view.php?id=2740 .
> 
> The solution to change oxstdurl and oxseourl fields to varchar(2048)
> currently sounds the best.
> 
> Also, to select good indexing length we would need feedback about usual
> lengths of these data in real shops. 
> Please help us by gathering some statistical data about these data in
> your shop database. 
> Could you please run the following query and send us the results? (just
> post the results here in the dev general)
> 
> SELECT oxstdurl,oxseourl FROM `oxseo` PROCEDURE ANALYSE(1,1);
> 
> together with data count returned by
> 
> SELECT count(*) FROM oxseo;
> 
> if it wouldn't work (e.g. some mysql clients automatically append limit
> clause after procedure), you could also use simple sql such as:
> 
> select count(*), avg(length(oxstdurl)), max(length(oxstdurl)),
> avg(length(oxseourl)), max(length(oxseourl)) from oxseo;
> 
> 
> Note, that on huge databases these selects will increase load.
> Especially if your database is already under heavy load, 
> it would be best to run it on a separate db clone or at least on more
> idle hours.
> 
> 
> Regards,
> Sarunas
> 
> 
> On Tue, 2011-04-26 at 16:01 +0200, anzido GmbH wrote:
> > Hi,
> > 
> > 
> > > I think it would be useful, to change the oxstdurl to an varchar-type and 
> > > impose this column with an index?
> > 
> > It's not only "useful" - it's absolutely essential if you have a big shop 
> > with much traffic!
> > Also you should take care that searching for seo urls is done only if the 
> > std url CAN HAVE any seo url. For example if the std url looks like: 
> > index.php?force_sid=  OR index.php?stoken= OR index.php? 
> > cl=search  and so on - there is NO seo url and searching for it is 
> > absolutely needless and a waste of ressources.
> > 
> > On one of our bigger projects we reduced the total number of sql queries by 
> > nearly 20%!
> > 
> > 
> > Beste Grüße aus Dortmund! 
> > Andreas Ziethen | Geschäftsführung 
> > 
> 
> 
> ___
> 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] oxseo fullscan

[Tobias Merkl]

count(*)avg(length(oxstdurl))   max(length(oxstdurl))   
avg(length(oxseourl))   max(length(oxseourl))
173199  116.8874404 74.6858 
325


173199



Kindest regards


Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Šarunas 
Valaškevicius
Gesendet: Mittwoch, 27. April 2011 13:06
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] oxseo fullscan

Hi,

we are currently fixing this issue,
https://bugs.oxid-esales.com/view.php?id=2740 .

The solution to change oxstdurl and oxseourl fields to varchar(2048)
currently sounds the best.

Also, to select good indexing length we would need feedback about usual
lengths of these data in real shops. 
Please help us by gathering some statistical data about these data in
your shop database. 
Could you please run the following query and send us the results? (just
post the results here in the dev general)

SELECT oxstdurl,oxseourl FROM `oxseo` PROCEDURE ANALYSE(1,1);

together with data count returned by

SELECT count(*) FROM oxseo;

if it wouldn't work (e.g. some mysql clients automatically append limit
clause after procedure), you could also use simple sql such as:

select count(*), avg(length(oxstdurl)), max(length(oxstdurl)),
avg(length(oxseourl)), max(length(oxseourl)) from oxseo;


Note, that on huge databases these selects will increase load.
Especially if your database is already under heavy load, 
it would be best to run it on a separate db clone or at least on more
idle hours.


Regards,
Sarunas


On Tue, 2011-04-26 at 16:01 +0200, anzido GmbH wrote:
> Hi,
> 
> 
> > I think it would be useful, to change the oxstdurl to an varchar-type and 
> > impose this column with an index?
> 
> It's not only "useful" - it's absolutely essential if you have a big shop 
> with much traffic!
> Also you should take care that searching for seo urls is done only if the std 
> url CAN HAVE any seo url. For example if the std url looks like: 
> index.php?force_sid=  OR index.php?stoken= OR index.php? 
> cl=search  and so on - there is NO seo url and searching for it is absolutely 
> needless and a waste of ressources.
> 
> On one of our bigger projects we reduced the total number of sql queries by 
> nearly 20%!
> 
> 
> Beste Grüße aus Dortmund! 
> Andreas Ziethen | Geschäftsführung 
> 


___
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] oxseo fullscan

[Tobias Merkl]

Hey community,

does anybody have an idea, why the oxseo-table doesn´t have an index?

I think it would be useful, to change the oxstdurl to an varchar-type and 
impose this column with an index? 

Kindest regards

Tobias


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*



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

Re: [oxid-dev-general] Extending db in 4.5

[Tobias Merkl]

In oxid 4.5 ce/pe you also have to update the views.

Service -> tools

Regards

Tobias



Am 14.04.2011 um 16:39 schrieb "Kai Gazmaga" 
mailto:kai.gazm...@vektordesign.de>>:

Hello,

as soon as I add a collumn to oxcategories or oxarticles no articles are listed 
in the backend of 4.5beta4 anymore. The frontend still works. What's the clue?

Best regards,

Kai Gazmaga
VektorDesign - Online-Shops und Programmierung
Kai Gazmaga
Neue Strasse 83
89 073 Ulm  Tel.: +49 731 - 3781953
Fax: +49 731 - 3781952
Mail:  
i...@vektordesign.de
Web:  
www.vektordesign.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] oxpec_class_file_paths.php not completely written

[Tobias Merkl]

Hey guys,

do you have more information or has somebody else the same problem?

We also have this hitch in some shops (4.4.6 and higher).

Kindest Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Aurimas Urbonas
Gesendet: Freitag, 25. März 2011 20:36
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] oxpec_class_file_paths.php not completely 
written

Hello,

https://bugs.oxid-esales.com/view.php?id=2214

Best regards,

Aurimas
On Fri, Mar 25, 2011 at 11:56 AM, Kai Gazmaga 
mailto:kai.gazm...@vektordesign.de>> wrote:
Hi!

today I came across a very irritating phenomenon: The shop of a customer was 
offline with an error-message that said, something in 
/tmp/oxpec_class_file_paths.php was wrong. Looking into the file made me see, 
it was not fully written. Line 65 looks like this:
'oxdeliverysetlist' => '/var/www/web4/html/LIVE/cor
deleting the file solved the problem. The customer told me the problem occurs 
for about a week after uploading article-pictures - not allways, but for some 
articles. Suddenly the complete system is unavailable (shop and admin). I will 
try to find out a bit more, but any hint would be helpful, becaus I did not 
find any bit of information on google or the forums.

Regards, Kai Gazmaga
VektorDesign - Online-Shops und Programmierung
Kai Gazmaga
Neue Strasse 83
89 073 Ulm

Tel.: +49 731 - 3781953
Fax: +49 731 - 3781952

Mail: i...@vektordesign.de<mailto:i...@vektordesign.de>
Web: www.vektordesign.de<http://www.vektordesign.de>




___
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

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

[Tobias Merkl]

Hey guys,

at the moment we have no category thumbnails in oxid, or?

Is this new in oxid 4.5? why only thumbnails and not multilingual category 
pics, icons and thumbs?

Kindest Regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Vilma 
Liorensaityte
Gesendet: Mittwoch, 30. März 2011 17:17
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Category thumbnail will be multilingual


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

Re: [oxid-dev-general] Important information

[Tobias Merkl]

Did you really mean 4.6?


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Arvydas
Gesendet: Dienstag, 8. März 2011 14:22
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Important information

Hi everybody,

Important information for module developers, partners.

Version 4.6 comes with improvements in session handling logic. One of the 
major change
will be forced (on user registration, login etc.) usage of 
session_regenerate_id() function,
which regenerates active session id.

Review your modules if this change may affect existing modules.

Regards
Arvydas Vapsva 

___
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] modules/functions.php in copy_this in latest update - bad idea!

[Tobias Merkl]

Hey guys,

this also applies for the cust_lang-files ;-)

Kindest regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Stefan Moises
Gesendet: Freitag, 4. Februar 2011 11:39
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] modules/functions.php in copy_this in latest update 
- bad idea!

Hi list,

I think it is a very bad idea to put the functions.php file into the 
"copy_this" folder for an update, because the file is supposed to be 
modified by shop users and with the latest update all changes will be 
lost if somebody doesn't pay close attention during the update and 
uploads it ... and if the user doesn't have SVN or something he will be 
really angry I guess...
Especially if he finds out that all that has changed was the date in the 
copyright notice ;)

@OXID: could you please remove that file from the update or at least put 
it into "changed_full" for updates?

Best regards,
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
***


___
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] Admin-Modules 4.3 incompatibility

[Tobias Merkl]

Hi Philip,

look here:

http://blog.tabsl.eu/programmierung/oxid-eshop-4-3-0-und-immer-kommt-der-adm
inlogin/

Kindest regards

Tobias Merkl
Software-Entwicklung


*
shoptimax GmbH
Guntherstraße 45a
90461 Nürnberg
Tel(09 11) 2 55 66 - 25
Fax(09 11) 2 55 66 - 29
eMail  me...@shoptimax.de
Webwww.shoptimax.de
*
Geschäftsführung: Friedrich Schreieck
Ust.-IdNr.: DE 814340642
Amtsgericht Nürnberg HRB 21703
*



-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Philip Frank
Gesendet: Donnerstag, 17. Juni 2010 10:45
An: 'dev-general@lists.oxidforge.org'
Betreff: [oxid-dev-general] Admin-Modules 4.3 incompatibility

Hi,

we have the issue that severalal Modules designed for Versions < 4.3 that
add new pages to the admin interface are incompatible with the 4.3 version.
Whenever you try to open the admin page you get redirected to the login.

We had some module vendors fix that problem, I was just wondering if anybody
knows what exactly causes it so we could get this done faster.

Regards,
Philip

Datenwerk GmbH - Mauerkircherstraße 8 - 81679 München
Tel.: 089 997383-223 Fax: 089 997383-10
Registergericht München - HRB 120556
Geschäftsführer: Tino Schöninger

___
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] Extending oxBase or getting manufacturers list in index page.

[Tobias Merkl]

Hello Darius,

have a look into _left.tpl and $oView->getVendorlist().

Kindest regards

Tobias



-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Mathias
Fiedler
Gesendet: Freitag, 4. September 2009 13:00
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Extending oxBase or getting manufacturers
list in index page.

Hello Darius,

what you need is a getter (for the manufacturers) accessible in all  
your templates, right?
If yes you could make a module of oxviewConfig to access this getter  
in all templates via $oViewConf->getXYZ()
or you could extend or write a own component to solve that task ...

@Tomas: I'm looking forward to hear more ideas about extending base  
classes

Bye
Mathias

Am 04.09.2009 um 09:00 schrieb Darius Tumas:

> Hello,
>
> I need to output manufacturers list with logos in index page  
> (homepage). As
> i understand i need to extend oxBase class, so that in all templates  
> method
> loadManufacturerList() could be accessible.
>
> Is there a way to do that without modifing core oxBase.php and  
> adding to it
> thous methods? Cause in this situation extending it throw modules  
> system
> does not work.
>
>
> Respectfully,
>
> Darius Tumas
>
> Tel.: +370 63113666
> ___
> 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