from:"Jens Trant"

V6 to big metapackages, what about suggests?

2018-04-11 Thread Jens Trant

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


[Closed]


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

Re: EE 5.3.7 migration to EE 6.0.2 is buggy

2018-04-10 Thread Jens Trant

Additional Info:
There seems to be no data loss during activation of the fatchip PayOne plugin, 
my data loss was caused by our internal verification/integration test. Sorry 
for the misleading information.

Thanks,
Jens-Christopher Trant



[Closed]<http://www.closed.com/>


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

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

Von: Jens Trant <jens.tr...@closed.com>
Datum: Dienstag, 10. April 2018 um 13:22
An: "dev-general@lists.oxidforge.org" <dev-general@lists.oxidforge.org>
Betreff: EE 5.3.7 migration to EE 6.0.2 is buggy

Hi guys,

I spent yesterday only a few hours for a test migration from EE 5.3.7 to 6.0.2, 
which seems to be actually buggy.
Maybe there is a newer/more compatible source for migrations which I have 
missed?!
My source was the official documentation: 
https://docs.oxid-esales.com/developer/en/6.0/update/eshop_from_53_to_6/database.html

Below you can see the results of the short test migration and possible 
solutions for common errors in the migration process.


The migration SQL script seems to have some bugs (migrate_ee_5_3_to_6_0.sql):
- All shop names will be replaced, the update command for CE & PE is not 
modified for EE users in the EE script
-> To solve this you have to remove OXNAME = 'OXID eShop 6' on line 10

- If you use MySQL >= 5.7  strict mode is by default active and NO_ZERO_DATE 
and NO_ZERO_IN_DATE is set in the sql_mode option by default, the migrate 
script will produce fatal errors by many statements.
-> You can solve this by adding SET @@session.sql_mode = ''; to the beginning 
of the script


Further if you used the Fatchip PayOne module in the CE, PE or EE before, you 
are not able to activate this module after migration in the backend (Error: 
Module could not be loaded).
- This is caused by the new module path (fc/fcpayone) and the old encoded 
oxconfig values in the database where the path is still the old one (fcPayOne). 
I tried two options for trying to fix this, but both will result in loosing 
data (all fatchip transaction tables are empty after activation)!

-> Option A: Set a symlink in the modules directory for fcPayOne -> fc/fcpayone
-> Option B: Update the 'aModulesPaths' in oxconfig via SQL
-> SQL:
UPDATE `oxconfig`
SET `OXVARVALUE` = ENCODE(
REPLACE (
DECODE
(
OXVARVALUE
,'YOUR_ENCODING_KEY'
)
,";s:8:\"fcpayone\";s:8:\"fcPayOne\";"
,";s:8:\"fcpayone\";s:11:\"fc/fcpayone\";"
)
,'YOUR_ENCODING_KEY'
)
WHERE OXVARNAME = 'aModulePaths';

I also noticed that the GitHub page of the PayOne module (which is already 
bundled with Oxid v6) says: 'Please note, that this extension is not yet 
released in production.' (https://github.com/PAYONE-GmbH/oxid-6), obviously the 
description is outdated.

I Hope the information will help some of you, feel free to share this in 
forums/social media/mails/or anything else you prefer ;)

Thanks,
Jens-Christopher Trant



[Closed]<http://www.closed.com/>


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

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

EE 5.3.7 migration to EE 6.0.2 is buggy

2018-04-10 Thread Jens Trant

Hi guys,

I spent yesterday only a few hours for a test migration from EE 5.3.7 to 6.0.2, 
which seems to be actually buggy.
Maybe there is a newer/more compatible source for migrations which I have 
missed?!
My source was the official documentation: 
https://docs.oxid-esales.com/developer/en/6.0/update/eshop_from_53_to_6/database.html

Below you can see the results of the short test migration and possible 
solutions for common errors in the migration process.


The migration SQL script seems to have some bugs (migrate_ee_5_3_to_6_0.sql):
- All shop names will be replaced, the update command for CE & PE is not 
modified for EE users in the EE script
-> To solve this you have to remove OXNAME = 'OXID eShop 6' on line 10

- If you use MySQL >= 5.7  strict mode is by default active and NO_ZERO_DATE 
and NO_ZERO_IN_DATE is set in the sql_mode option by default, the migrate 
script will produce fatal errors by many statements.
-> You can solve this by adding SET @@session.sql_mode = ''; to the beginning 
of the script


Further if you used the Fatchip PayOne module in the CE, PE or EE before, you 
are not able to activate this module after migration in the backend (Error: 
Module could not be loaded).
- This is caused by the new module path (fc/fcpayone) and the old encoded 
oxconfig values in the database where the path is still the old one (fcPayOne). 
I tried two options for trying to fix this, but both will result in loosing 
data (all fatchip transaction tables are empty after activation)!

-> Option A: Set a symlink in the modules directory for fcPayOne -> fc/fcpayone
-> Option B: Update the 'aModulesPaths' in oxconfig via SQL
-> SQL:
UPDATE `oxconfig`
SET `OXVARVALUE` = ENCODE(
REPLACE (
DECODE
(
OXVARVALUE
,'YOUR_ENCODING_KEY'
)
,";s:8:\"fcpayone\";s:8:\"fcPayOne\";"
,";s:8:\"fcpayone\";s:11:\"fc/fcpayone\";"
)
,'YOUR_ENCODING_KEY'
)
WHERE OXVARNAME = 'aModulePaths';

I also noticed that the GitHub page of the PayOne module (which is already 
bundled with Oxid v6) says: 'Please note, that this extension is not yet 
released in production.' (https://github.com/PAYONE-GmbH/oxid-6), obviously the 
description is outdated.

I Hope the information will help some of you, feel free to share this in 
forums/social media/mails/or anything else you prefer ;)

Thanks,
Jens-Christopher Trant




[Closed]


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

AGB / Terms and conditions checked does not work in checkout

2017-01-05 Thread Jens Trant

Hey guys,

kindly let you know that the built-in terms and conditions check in the 
checkout process does not work (always accepted) if you use the shipped PayOne 
module with OXID (EE, maybe also PE).
The mistake is in the 'fcPayOneOrderView.php' which is shipped with in OXID EE 
(maybe also PE) on line 347:

if(parent::_validateTermsAndConditions() === true); {

Should be:
if(parent::_validateTermsAndConditions() === true) {


The semicolon ignores the condition so that the 'if-block' (which actually does 
not belong to the if) is executed always!

Also see my reported issue at:
https://bugs.oxid-esales.com/view.php?id=6568

Have a nice day, cheers,
Jens-Christopher Trant



[Closed]


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

Re: [oxid-dev-general] Quick SOAP ERP Connector question

2016-04-29 Thread Jens Trant

Can you reach the endpoints via soapUI (it is a really nice charming tool), 
maybe you have a network/proxy issue?
Https is not necessary, are the shop urls correctly set in the config.inc.php? 
So be sure, that there is also no redirect.

Cheers,
Jens




[Closed]<http://www.closed.com/>


Closed GmbH  |  Straßenbahnring 6  |  20251 Hamburg  |  Germany
T +49 40 441840 865  |  E jens.tr...@closed.com<mailto:jens.tr...@closed.com>
closed.com<http://closed.com>  |  
facebook.com/closed<https://www.facebook.com/closed> 
<http://www.facebook.com/closed>  |  instagram.com/closedofficial 
<https://www.instagram.com/closedofficial/>

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

Von: 
<dev-general-boun...@lists.oxidforge.org<mailto:dev-general-boun...@lists.oxidforge.org>>
 im Auftrag von Mirza Ahtasham Ahmad 
<ahtasha...@gmail.com<mailto:ahtasha...@gmail.com>>
Antworten an: 
"dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>" 
<dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>>
Datum: Freitag, 29. April 2016 um 11:23
An: "dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>" 
<dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] Quick SOAP ERP Connector question

I have already tried it


//$client = new 
SoapClient("https://myshopurl.de/modules/erp/oxerpservice.wsdl;);
or
//$client = new 
SoapClient("https://myshopurl.de/modules/erp/oxerpservice.php?wsdl=2.14.0;);
or
$client = new 
SoapClient("https://myshopurl.de/modules/erp/oxerpservice.wsdl?version=2.14.0;);

with the last version i am getting the following error...

Fatal error: Uncaught SoapFault exception: [WSDL] SOAP-ERROR: Parsing WSDL: 
Couldn't load from 
'https://myshopurl.de/modules/erp/oxerpservice.php?wsdl=2.14.0' : 
failed to load external entity 
"https://myshopurl.de/modules/erp/oxerpservice.php?wsdl=2.14.0; in 
C:\wamp\www\apirequest.php:6 Stack trace: #0 C:\wamp\www\apirequest.php(6): 
SoapClient->SoapClient('https://www.cac...') #1 {main} thrown in 
C:\wamp\www\apirequest.php on line 6




could it be that https should be active...because right now it is a 
staging/test siteand we dont have https right now...

because the url in Modul Docu...for Reading WSDL

==

For reading the WSDL, call the URL

https://www.myeshop.com/oxideshop/modules/erp/oxerpservice.php?wsdl=2.14.0

==

=>

https://www.myeshopurl.de/modules/erp/oxerpservice.php?wsdl=2.14.0

is also not working.







Mit freundlichen Grüßen | Warm Regards,

Mirza Ahtasham Ahmad
M +4917645387460 | Skype: ahtasham82





On Fri, Apr 29, 2016 at 11:14 AM, Jens Trant 
<jens.tr...@closed.com<mailto:jens.tr...@closed.com>> wrote:

Hi,

You have to specify the version otherwise you get the really first version from 
the ERP module:
https://shopurl.com/modules/erp/oxerpservice.wsdl?version=2.14.0

Cheers,
Jens



[Closed]<http://www.closed.com/>


Closed GmbH  |  Straßenbahnring 6  |  20251 Hamburg  |  Germany
T +49 40 441840 865<tel:%2B49%2040%20441840%20865>  |  E 
jens.tr...@closed.com<mailto:jens.tr...@closed.com>
closed.com<http://closed.com>  |  
facebook.com/closed<https://www.facebook.com/closed> 
<http://www.facebook.com/closed>  |  instagram.com/closedofficial 
<https://www.instagram.com/closedofficial/>

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

Von: 
<dev-general-boun...@lists.oxidforge.org<mailto:dev-general-boun...@lists.oxidforge.org>>
 im Auftrag von Mirza Ahtasham Ahmad 
<ahtasha...@gmail.com<mailto:ahtasha...@gmail.com>>
Antworten an: 
"dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>" 
<dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>>
Datum: Freitag, 29. April 2016 um 10:55
An: "dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>" 
<dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>>
Betreff: [oxid-dev-general] Quick SOAP ERP Connector question

Hi,

I have a EE 5.2.7 installed. I also installed the ERP Connector module on it.

Now I wanted to test if the SOAP service for ERP is working or not so I am 
trying to make a request from my local computer to the shop setup on hosting 
server.

How Can I do that I did make a SOAP request to the following url

http://myshopurl.de/modules/erp/oxerpservice.wsdl

like this...

$client = new SoapClient("http://myshopurl.de/modules/erp/oxerpservice.wsdl;);

$result = $

V6 to big metapackages, what about suggests?

Re: EE 5.3.7 migration to EE 6.0.2 is buggy

EE 5.3.7 migration to EE 6.0.2 is buggy

AGB / Terms and conditions checked does not work in checkout

Re: [oxid-dev-general] Quick SOAP ERP Connector question

5 matches

Site Navigation

Mail list logo

Footer information