AW: localized offline.html

2017-04-12 Thread Marat Bedoev 
Or just a static html page with javascript browser language detection that 
shows content in particular language.

-Ursprüngliche Nachricht-
Von: Stephan Bauer [mailto:i...@stephanbauer.info] 
Gesendet: Mittwoch, 12. April 2017 16:00
An: dev-general@lists.oxidforge.org; scho...@primus-print.de
Betreff: Re: localized offline.html

Hi Robert,

I think there is no solution except of writing an extension.

You could write an extension, that extends oxutils.php (redirectOffline
($iHeaderCode=302)) and redirects to different files (e.g.
offline_de.html) dependent on the language.

Regards

Stephan Bauer

Am 12.04.2017 um 14:59 schrieb Robert Schöne:
> Hi there!
> Is there a solution to have a localized offline.html ?
> We run shops in different languages and it is somehow unconvenient to 
> have a maintenance page that is not in the native language of that shop.
> Do we overlook something?
> Thanks for your help on that issue.
>
> Best regards,
> Robert Schöne

Re: [oxid-dev-general] ERP Module Issues

2016-07-15 Thread Marat Bedoev 
Did you try asking OXID support? Cause this mailing list is not a support 
channel

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Mirza Ahtasham 
Ahmad
Gesendet: Donnerstag, 14. Juli 2016 20:30
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] ERP Module Issues

Hi,

Can nobody help me regarding ERP Logging?? Anyone from OXID Guys ?? Atleast 
anyone from OXID should help regarding their ERP Connector. It says in docs...

ERP version 2.10.0 and higher has SOAP communication debugging possibility 
implemented. It enables logging of full SOAP requests and responses by adding 
the following configuration constant to shop’s config.inc.php file:

but it is only logging the RESPONSE and not REQUEST.

Without the REQUEST Log I cannot debug my issue that I am having.









Mit freundlichen Grüßen | Warm Regards,

Mirza Ahtasham Ahmad
M +4917645387460 | Skype: ahtasham82





On Tue, Jul 12, 2016 at 9:33 AM, Reinhard Vogl 
mailto:reinhard.v...@deutschedaten.de>> wrote:
Hi,

Idea for 1.)
Can you look for your Mall settings?
If you enabled the option “Indiv. Preis für vererbte Artikel erlauben”, the 
prices are stored in the table oxfield2shop.
Be sure, that you need individual process for inheritance, because it slows 
down ERP import a lot.

2.) rsync is your friend

Greets,
Reini

Von: 
dev-general-boun...@lists.oxidforge.org
 
[mailto:dev-general-boun...@lists.oxidforge.org]
 Im Auftrag von Mirza Ahtasham Ahmad
Gesendet: Dienstag, 12. Juli 2016 09:26
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] ERP Module Issues

​1. It is saving the values in OXID. what I am trying to say is that the 
transfer from ERP to OXID does happen as I posted the SOAP Response, I get the 
Posted Article ID and blResult is true and I see the article in OXID Backend. 
But I only the Price is not being saved. Because all the Price fields in OXID 
are empty. I assume the ERP is not sending the correct request, meaning it is 
not sending the price in the correct parameter.

For that I wanted to check the log​s but there is another problem with logs. 
The logs of the ERP Module, only prints the RESPONSE in erp.log file and not 
the REQEUST so I cannot varify my hypothesis that the ERP is sending wrong 
REQUEST.

Therefore at first, I need to fix the Logging Problem of ERP Connector. Has 
anyone a suggestion there ?



2. With image transfer, thats what I thought, that the ERP Connector only saves 
the DB Fields values such as pic name in oxpic fields but not actually 
transfers the image file. For that I will have to write a routine that uploads 
the images to the correct directories. I just wanted to be sure, not that I 
have missed something in configuration of ERP Module. Thanks.


I will be grateful if someone can help me out with the Logging problem.

Thanks,












Mit freundlichen Grüßen | Warm Regards,

Mirza Ahtasham Ahmad
M +4917645387460 | Skype: ahtasham82





On Mon, Jul 11, 2016 at 7:36 PM, Michael Bladowski 
mailto:mbladow...@macropage.de>> wrote:
dear mirza,
Am 11.07.2016 um 18:29 schrieb Mirza Ahtasham Ahmad:
Hi Guys,

I have a Shop version EE 5.2.7. I have also installed the ERP Connector 
MOD_ERP_2.14.1_OXID_ESHOP_EE_5.2.1_4.9.1_for_PHP5.6

I have 2 issues that I am facing.

1. The Product Price is not being transfered to oxid shop. I am getting back a 
response with Product OXID and blResult as true in return.



if the values are changed in DB but not at the frontend, clear (the front-end) 
cache, if you are using one.
if the values are not changed in DB, i guess the request itself has an error, 
wrong format, wrong oxid, unwanted
chars inside request, there are many things, did you test it with any other 
field than price ? before you use php
(or any other coding lang) i recommend to setup a working call with 
soapui, to be 100% sure your 
problems are
not realted to the shop.


2. Issue is more a How To QuestionHow can I transfer the images of products 
and categories. via ERP SetArticle method image names can be sent to shop but 
the image file, how can it be transfered on the server. The ERP that is being 
used is "Comarch-ERP" there you can give the FTP Username and password where 
the files can be uploaded but in OXID all the master paths for product and 
categories are different so thats why I am unable to transfer the product 
images.

i don´t know all the specs about the latest oxid, but for me the best solution 
has always been, NOT using the ERP api.
as i know the ERP api, its only for changing DB data, nothing that is related 
to the filesystem (okay, if you delete an item, the images get deleted, but
i don´t speak about internal things like that) ;) i don´t know whats best 
practise but i always try to keep the i

Re: [oxid-dev-general] Umstimmigkeiten bei LESS-Compile Mobile-Theme 1.2.1 -> 1.3.0

2015-08-17 Thread Marat Bedoev 
Hi,

the original precompiled oxid.css also contais mentioned css code:
https://github.com/OXID-eSales/mobile_theme/blob/b-1.3/theme/source/out/mobile/src/css/oxid.css#L1534
https://github.com/OXID-eSales/mobile_theme/blob/b-1.3/theme/source/out/mobile/src/css/oxid.css#L1557

the row number differences may occur because of different compiler, different 
compilation params or even a different version oft he same compiler.

For my templates, i usually stick tot he original compiler and the particular 
version used/suggested by framework developer. 


Cheers


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von wolkenkrieger
Gesendet: Montag, 17. August 2015 11:54
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Umstimmigkeiten bei LESS-Compile Mobile-Theme 
1.2.1 -> 1.3.0

Hello :)

Due an upgrade of the Mobile Theme from v 1.2.1 to 1.3.0 the following problem 
occured:

Winmerge says, that the LESS-files in the 1.3.0-downloadpackage are identical 
to the v 1.2.1. So ... if i recompile these files to an oxid.css i should get 
an oxid.css, which is also identical to the oxid.css in the 
1.3.0-downloadpackage.

But it isn't!

In the fresh compiled version are additional styles ( 
.btn-warning[disabled]:focus, ; .btn-danger.disabled:focus ) AND the order of 
some styles are different.

How can this happen?

Imho the oxid.css in the 1.3.0-downloadpackage was not compiled with the 
LESS-files from this package.

Thanks :)

wolke

P.S. sorry for the poor english - i did my best^^

Am 17.08.2015 um 11:02 schrieb Marco Steinhaeuser:
> Hey,
>
> could you please repeat your request in English? Otherwise some people 
> on this list will not understand, especially those you want to answer 
> your request ;)
>
> Cheers
> Marco
>
> 
> From: dev-general-boun...@lists.oxidforge.org 
> [dev-general-boun...@lists.oxidforge.org] on behalf of wolkenkrieger 
> [wolkenkrie...@gmail.com]
> Sent: Friday, August 14, 2015 6:37 PM
> To: dev-general@lists.oxidforge.org
> Subject: [oxid-dev-general] Umstimmigkeiten bei LESS-Compile Mobile-Theme 
>   1.2.1 -> 1.3.0
>
> Hallo in die Runde (oder wie auch immer man sich hier meldet) :)
>
> Im Zuge der Umstellung einer CE 4.8.7 auf die aktuelle 4.9.5 wurde 
> auch das Mobile Theme von der 1.2.1 auf die 1.3.0 umgestellt.
>
> Dabei fiel Folgendes auf:
>
> Laut Winmerge sind die LESS-Files identisch - also sollte auch die 
> daraus resultierende oxid.css identisch sein, wenn man sie aus den 
> vorliegenden LESS-Files neu kompiliert.
>
> ABER: in der neu erstellten oxid.css sind Styleangaben enthalten
> (Beispiele: .btn-warning[disabled]:focus, ; .btn-danger.disabled:focus 
> ), die es in der oxid.css aus dem Downloadpackage nicht gibt. 
> Ausserdem tauchen Styleangaben in der neu komplierten Version an 
> anderer Stelle auf (Zeilennummer - selbst, wenn man remarks usw. entfernt).
>
> Nach meinem Verständnis müsste bei einer Neukompilation mit den 
> LESS-Files aus dem Downloadpackage exakt die oxid.css - Version 
> herauskommen, die auch im Downloadpackage enthalten ist - es sei denn, 
> die Downloadversion wurde nicht mit den LESS-Files aus dem 
> Downloadpackage kompiliert?!
>
> Wie sieht's hier also aus?
>
> Danke und Gruß
>
> wolke
> ___
> 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
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Better block definition in original templates

2015-03-17 Thread Marat Bedoev 
Sure,
i faced same problem several times. feel free to make a pull request :)

If you need a quick workaround:
https://github.com/vanilla-thunder/vt-cmsstructure/blob/master/copy_this/modules/vt-cmsstructure/out/blocks/admin_content_list_item.tpl


-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Maximilian 
Berghoff
Gesendet: Dienstag, 17. März 2015 12:12
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Better block definition in original templates

Hi,

i really like the idea of blocks in the templates. The upside is, that i don't 
need to copy the complete template for changes. Template changes in the 
original code arn't that hard to catch, when just extending some blocks.

But i think there are some block definitions in the shop code that arn't very 
helpfull. Example

[{bloc="block-name"}]

 
 

[{/block}]
(seen in basketcontents.tpl)

It is impossible now to extend the  content except copying the 
complete content again.

Better approach:


[{bloc="block-name"}]

 
 
[{/block}]


Now i can just extend the block and add my content.

What do you think?

greets max
--

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

Re: [oxid-dev-general] Clickable logo in the module setting

2015-03-17 Thread Marat Bedoev 
Hello,

you can insert clickable logo in module description, like here:
https://github.com/vanilla-thunder/bla-tinymce/blob/master/copy_this/modules/bla/bla-tinymce/metadata.php

for module settings you can use html code in language idents for your settings:
https://github.com/vanilla-thunder/bla-tinymce/blob/master/copy_this/modules/bla/bla-tinymce/views/admin/de/module_options.php


cheers

-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Maximilian 
Berghoff
Gesendet: Dienstag, 17. März 2015 12:01
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Clickable logo in the module setting


hi,

i have a question if somebody ever tried to put the url (metadata.php) under 
the thumbnail (metadata.php) to make it clickable?
We tried to extend the template. Yea that works when the module is active - the 
template exists, so i can add a link into that template, but when deactivating 
the template it does not exist anymore -> Exception.

any help? any hints?

greets max

--

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

Re: [oxid-dev-general] Modify a template where is no block

2015-01-20 Thread Marat Bedoev 
Hi,
tell your customers to add a custom block to the template, so you can override 
it.

cheers

-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alex Schwarz
Gesendet: Dienstag, 20. Januar 2015 16:03
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Modify a template where is no block

Hello,

for a module, I want to modify a part of a azure template
(order_cust.tpl) that is _not_ inside a block. What is the best practice to do 
that?
I don't want to have my customers install a custom theme, which inherites from 
azure - is there a better option?

Best regards

--
Alexander Schwarz
___
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 Page type Upper Menu

2015-01-19 Thread Marat Bedoev 
Actually the top menu you are talking about isn’t top menu you think it would 
be.

Earlier, with the basic template there were a category menu on the left side 
and a cms pages menu on top.
With Azure the category menu moved on top oft he page and the original top menu 
kind of disappeared.

Add this code to the sidebar:
[{if $oView->getMenueList() }]
   [{foreach from=$oView->getMenueList() item="_cms"}]
  
[{$_cms->oxcontents__oxtitle->value}]
  
[{/foreach}]
[{/if}]


Cheers!

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Mirza Ahtasham 
Ahmad
Gesendet: Freitag, 16. Januar 2015 17:25
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] CMS Page type Upper Menu

Thanks,

so I have understood it correctly, it should come up in the top menu?? just 
like if you create a Category Type page it appears in the top menu ?? If yes 
then what is the difference when both will appear in the top menu?

@Dev-Oxid
The bug is more than 2 years old, any update here ??

Thanks,








Mit freundlichen Grüßen | Warm Regards,

Mirza Ahmad
M +4917645387460 | Skype: ahtasham82





On Fri, Jan 16, 2015 at 5:16 PM, Martin Wegele 
mailto:martin.weg...@oxid-esales.com>> wrote:
This is a known issue: https://bugs.oxid-esales.com/view.php?id=4404



Von: 
dev-general-boun...@lists.oxidforge.org
 
[dev-general-boun...@lists.oxidforge.org]"
 im Auftrag von "Mirza Ahtasham Ahmad 
[ahtasha...@gmail.com]
Gesendet: Freitag, 16. Januar 2015 17:06
Bis: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] CMS Page type Upper Menu
Hi guys,

A quick question, under the CMS Pages in Adminstration panel. You can choose 
"Upper Menu" as a type for the CMS Content.

I created one CMS Content and assigned this type to it, I was expecting that it 
will appear in the top menu but it didn't. I dont see anywhere a Link for that 
newly created content page.

Can anybody tell me how this works ??



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

Re: [oxid-dev-general] Release orgy: OXID eShop 4.7.14, 4.8.8, 4.9.1 + ERP/SOAP + creditPass + PayPal

2014-10-31 Thread Marat Bedoev 
Hello,

since 4.9/5.2 the update cycle was changed to 3 months.

-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Michael Wagner
Gesendet: Donnerstag, 30. Oktober 2014 20:56
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Release orgy: OXID eShop 4.7.14, 4.8.8, 4.9.1 + 
ERP/SOAP + creditPass + PayPal

General questions about veröffendlichen of release.

Why can not this be done by a fixed deadline.
Hardly is an update comes out again one.

Although is nice when there are always updates. But one can not keep up with 
the updates.

I can currently not even the 4.9 update because some external modules are not 
komplatible with the 4.9.

A solid rhythm Währe some games. Every 3 months or so.

Michael Wagner (Spark 5)


Am 2014-10-29 16:38, schrieb Marco Steinhaeuser:
> Hi everybody,
>
> this could be called a release orgy. To make it more clear and 
> understandable, I put all information into a blog post:
> 
> http://blog.oxid-esales.com/2014/10/releasing-oxid-eshop-patches-suppo
> rted-series-new-erp-interface-creditpass-module-paypal-module-versions
> /
>
> Enjoy and don't hesitate to request in this thread if something is not 
> clear etc...
>
> Cheers
> Marco
> ___
> dev-general mailing list
> dev-general@lists.oxidforge.org
> http://dir.gmane.org/gmane.comp.php.oxid.general

--
--
Michael Wagner
Seniore Software Developer
--
Spark 5 GmbH
Rheinstr. 97
64295 Darmstadt
Germany
--
Fon: +49-6151-8508-027
Fax: +49-6151-8508-111
Mail: michael.wag...@spark5.de
Web: http://www.spark5.de
--
Geschäftsführer:
Henrik von Wehrs
Amtsgericht Darmstadt, HRB 7809
___
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] Paypal Redirect

2014-10-15 Thread Marat Bedoev 
Hello,
In this case you should try another paypal modules / integrations for oxid. 
There are several modules on exchange.

Keep in mind, that with your sceario you will have a new ordner in your shop 
even if user will not pay. (e.g. because of internet conenction problems, user 
went afk and session timed out, js blocker addons) And on the other hand user 
cant go back and use another payment method or change shipping address.



Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Hardik Badani
Gesendet: Mittwoch, 15. Oktober 2014 12:29
An: Dev General
Betreff: [oxid-dev-general] Paypal Redirect

Hello All,

I have one query regarding default paypal module in OXID.

After successfully integrates, It redirects to paypal site from step-3 and on 
successful payment it returns back to step-4, where further we need to submit 
order.
It is bit confusing flow for our customer.

So, they want us to redirect to paypal site from step-4 and on successful 
payment they want it to return back directly on thank you page.

Can we somehow modify this..?

If anyone can help here, it would be much more appreciates.

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

Re: [oxid-dev-general] Security improvement: Dynamic security token check

2014-09-30 Thread Marat Bedoev 
Hello,

i'm a bit confused. We use tobasket-urls on external pages like bundle/product 
configurator, to add the products to basket.
So, if a user who is already logged in the shop would click on the link on 
external page, the check would fail and nothing will happen?
But users who are not logged in, will get the products added to their baskets?

Thank you,
Marat


Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Tomas Liubinas
Gesendet: Dienstag, 30. September 2014 10:13
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Security improvement: Dynamic security token 
check

Hi everyone,

last week I informed about the stoken check to be expected, remember? I reach 
out today to let you know that we had to update the behavior before the present 
release:

Basically the change is that stoken now is checked not for every form but only 
for forms intended for the logged in users. Adding the "tobasket" link could be 
perfromed by anonymous users therefore stoken is not checked and not validated 
in this case. As in our documentation we used the "tobasket" link as an 
example, we changed the documentation:
http://wiki.oxidforge.org/Downloads/4.9.0_5.2.0#Dynamic_Group_assignment_security_improvement

The note regarding not anymore supported features (adding to basket from 3rd 
party sites) was also removed. So no feature will be lost due to this security 
improvement.

Sorry for any inconvenience, didn't want to confuse you just let you know in 
time about the changes...

Regards
Tomas Liubinas

From: 
dev-general-boun...@lists.oxidforge.org
 [mailto:dev-general-boun...@lists.oxidforge.org] On Behalf Of Joscha Krug | 
marmalade GmbH
Sent: Thursday, September 25, 2014 5:10 PM
To: dev-general@lists.oxidforge.org
Subject: Re: [oxid-dev-general] Security improvement: Dynamic security token 
check

Hello Marco,

Thanks for the information!

Could someone from the devs explain the background? This will not be so easy to 
implement automaticly as i affects a lot of templates.

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
Am 25.09.2014 16:01, schrieb Marco Steinhaeuser:

Hi everybody,



just added an important section to the release notes of the upcoming OXID eShop 
version 4.9/5.2: The dynamic security token parameter check was expanded to all 
forms and action URLs. This is important for you to know especially if you're 
running functions like to_basket etc...



Read more about it here:

http://wiki.oxidforge.org/Downloads/4.9.0_5.2.0#Security_improvement:_Dynamic_security_token_check



Please head back for any questions about it and the other stuff at this release 
notes page.



Best regards!

Marco

___

dev-general mailing list

dev-general@lists.oxidforge.org

http://dir.gmane.org/gmane.comp.php.oxid.general

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

Re: [oxid-dev-general] OXID eShop Version 5.1.6 / 4.8.6 published

2014-06-06 Thread Marat Bedoev 
Try this one:
http://www.oxid-esales.com/en/community/download-oxid-eshop.html

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Beltran
Gesendet: Freitag, 6. Juni 2014 15:51
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID eShop Version 5.1.6 / 4.8.6 published

It seems 4.8.6 is not available for download. I'm trying to download at 
http://wiki.oxidforge.org/Downloads/4.8.6_5.1.6

Thanks.


On 06/05/2014 05:21 PM, Martin Wegele wrote:
Hi everyone,

OXID eShop version 5.1.6 (EE) and 4.8.6 (CE + PE) were published yesterday.
Please note that this patch release exceptionally contains changes in the 
templates of the Azure theme and one new field in the table oxarticles of the 
shop's database. These modifications were necessary to make the OXID eShop 
compliant with the new regulations of the Consumer Right Directive as we 
announced before in a blog post: 
http://blog.oxid-esales.com/2014/05/due-to-the-consumer-right-directive-new-releases-ahead/

As usual you will find all important information about these and other changes 
on the OXIDforge: http://wiki.oxidforge.org/Downloads/4.8.6_5.1.6
There you will also find a PDF-file which contains a detailed description of 
the changes related to the Consumer Right Directive so you can apply them to 
your shop manually.

Watch out for our newsletter and German blog post which will describe some of 
the changes with screenshots.

Next Tuesday we will publish version 5.0.12 (EE) and 4.7.12 (CE + PE) as a 
patch for the legacy branch which will also contain the mentioned changes.

Kind Regards,
Martin




___

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] Force recalculation of order

2014-06-03 Thread Marat Bedoev 
Hello,

sabe the order article after canceling it and before recalculating the order:

$oOrderArticle-> cancelOrderArticle ()
$oOrderArticle->save()

Cheers,
Marat


Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander 
Schwarz
Gesendet: Montag, 2. Juni 2014 17:04
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Force recalculation of order

Hello,

is there a way to recalculate an order after it is saved? I want to build 
functionality for partial return deliveries.

I tried to cancel some orderArticles with
$oOrderArticle->cancelOrderArticle();

after I called $oOrder->recalculateOrder()

and $oOrder->save()

But at the end, I have the same total sums. At least the canceled order article 
is not showing up in the invoice,
but the calculation is not touched.

Thanks in advance for any help on this.

Best regards,




Alexander Schwarz
Senior Web Developer


[cid:image001.jpg@01CF7F23.FD62FEA0]

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

Re: [oxid-dev-general] less

2014-03-21 Thread Marat Bedoev 
But the new full responsive template oxid wanted to release right after commons 
2013 will habe less/sass? :-P

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Marco 
Steinhaeuser
Gesendet: Donnerstag, 20. März 2014 20:46
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] less

Hi HJ,

no defined plans yet for Azure, sorry.

Best
Marco

From: 
dev-general-boun...@lists.oxidforge.org
 [dev-general-boun...@lists.oxidforge.org] on behalf of Hans Jürgen Fricke 
[h...@narendra.de]
Sent: Thursday, March 20, 2014 5:50 PM
To: dev-general@lists.oxidforge.org
Subject: [oxid-dev-general] less
Hi folks,

just testet the mobile Template with css-less. Great.
Are there any plans to include less in azure?


Hans Jürgen Fricke

ladatta.de
Fon 0172 4217539
h...@ladatta.de
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] OXID caching CMS pages?

2014-02-18 Thread Marat Bedoev 
Hello,

before going live with you shop, you should disable the productive mode 
setting, it willl disable most caches. But disabling cache in a live shop will 
make it a lot slower.
Nut sure, if there are some special settings in EE or PE for cache lifetime, 
but i would not disable cache for cms pages. Clearing it manually is still the 
best option.
There are some addons which can help you clearing cache, e.g. 3D module 
connector
http://www.oxidmodule.com/Modul-Connector/Modul-Connector-fuer-Oxid-CE-PE-EE.html


cheers


Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Hans-Peter 
Szcazmus
Gesendet: Dienstag, 18. Februar 2014 16:22
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] OXID caching CMS pages?

Hi Marat,

thanks for your quick reply. Can it be disabled in the admin? If yes: How?

Best Regards,
Hans Peter


Gesendet: Dienstag, 18. Februar 2014 um 15:43 Uhr
Von: "Marat Bedoev" 
mailto:marat.bed...@heiner-direct.com>>
An: "dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>" 
mailto:dev-general@lists.oxidforge.org>>
Betreff: Re: [oxid-dev-general] OXID caching CMS pages?
Yes

Cheers,
Marat

Von: 
dev-general-boun...@lists.oxidforge.org<mailto:dev-general-boun...@lists.oxidforge.org>
 [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Hans-Peter 
Szcazmus
Gesendet: Dienstag, 18. Februar 2014 15:03
An: dev-general@lists.oxidforge.org<mailto:dev-general@lists.oxidforge.org>
Betreff: [oxid-dev-general] OXID caching CMS pages?

Dear developers,

just one little question: Does OXID cache CMS pages?
Sometimes I have the problem that changes that were made in the admin are only 
shown when i clear the tmp-dir.

Thanks in advance for your time and answers.

Best regards,
Hans Peter
___ 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] OXID caching CMS pages?

2014-02-18 Thread Marat Bedoev 
Yes

Cheers,
Marat

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Hans-Peter 
Szcazmus
Gesendet: Dienstag, 18. Februar 2014 15:03
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] OXID caching CMS pages?

Dear developers,

just one little question: Does OXID cache CMS pages?
Sometimes I have the problem that changes that were made in the admin are only 
shown when i clear the tmp-dir.

Thanks in advance for your time and answers.

Best regards,
Hans Peter
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Blocks save path changed in 4.8?

2014-01-21 Thread Marat Bedoev 
Check if the patch in the oxtplblocks table is correct, cause once the blocks 
are copied into the database, they will not be updated if metadata changes

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander Kludt
Gesendet: Dienstag, 21. Januar 2014 14:51
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Blocks save path changed in 4.8?

Hi,

thanks for your reply - but if I just keep the old structure it won't enter the 
blocks into oxtplblocks.
I moved them, reactivated the module - now he writes them to the table but 
still won't show them.
--
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.



[cid:image001.jpg@01CF16B9.2B1B6450]
Frank Zunderer
Dienstag, 21. Januar 2014 14:41
Hi,

i think it wasn't changed, it's still out/blocks if you specify only the 
filename, but it can be any folder if you specify with path from module folder.

Regards,
Frank Zunderer

Von: 
dev-general-boun...@lists.oxidforge.org
 [mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander Kludt
Gesendet: Dienstag, 21. Januar 2014 14:33
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Blocks save path changed in 4.8?

Hi guys,

from what I can see the blocks in 4.8 are now stored in

modules/mymodule/views/blocks

they used to be stored in

modules/mymodules/out/blocks

why the heck was that changed without any backward compatibility?
Was this mentioned anywhere? Did I miss anything?

--
best regards
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
[cid:image002.jpg@01CF16B9.2B1B6450]
Alexander Kludt
Dienstag, 21. Januar 2014 14:32
Hi guys,

from what I can see the blocks in 4.8 are now stored in

modules/mymodule/views/blocks

they used to be stored in

modules/mymodules/out/blocks

why the heck was that changed without any backward compatibility?
Was this mentioned anywhere? Did I miss anything?

--
___
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] Blocks save path changed in 4.8?

2014-01-21 Thread Marat Bedoev 
Hello,

in oxUtilsView->_getTemplateBlock()  (row 458) you can see, where OXID is 
looking for block templates.
In general you can place your block where ever you want but you need an 
absolute path to it in your metadata.php
If you do only have file's basename in your metadata.php, OXID will be looking 
for blocks in module/your-module/out/blocks/


greetings.
Marat

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Alexander Kludt
Gesendet: Dienstag, 21. Januar 2014 14:33
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Blocks save path changed in 4.8?

Hi guys,

from what I can see the blocks in 4.8 are now stored in

modules/mymodule/views/blocks

they used to be stored in

modules/mymodules/out/blocks

why the heck was that changed without any backward compatibility?
Was this mentioned anywhere? Did I miss anything?

--
best regards
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

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

2014-01-21 Thread Marat Bedoev 
Hello,

i prefer to keep modules as simple as possible and so i’m against extra module 
connectors.
One day you will have a module, that requires some changes in your connector, 
and the change in the connector will require to update all your modules.

Cheers,
Marat

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Marcel Müller
Gesendet: Dienstag, 21. Januar 2014 08:44
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Pros and cons for module-connectors

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.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Time to say good bye to OXID projects?

2012-12-14 Thread Marat Bedoev 
Hello,

OXID Projects is not OXID eShop!
OXID Projects contain some free opensource modules for OXID eSales.
This way the community can help with updating some modules or enhancing them. 
And on the other side: as developer you can always reply all the requests like 
"You have to  implement feature X and change Y and we also need some new 
function Z" with a freindly email like "its on github, do with it what ever you 
need/want".

In case of the german law about buttons:
we hat a patch and a workout for basic and azure templates. Perhaps you just 
didnt found it?
This "Button-Solution" is not a module. It requires a whole tutorial to tell 
non-programmes how and where to make new changes. And since some casual users 
even have problems with downloading archives from github and finding included 
manuals, i think the community forum is much better place for such tutorials.

Many greetings from germany and wish you all a nice weekend.

Der Inhalt dieser Nachricht ist ausschließlich für den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Nachricht oder dessen 
Vertreter sein sollten, so beachten Sie bitte, dass jede Form der 
Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser Nachricht 
unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der 
Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch einen 
Virenscanner auf Viren und sonstigen schädlichen Inhalt geprüft, jedoch wird 
keinerlei Haftung für Schäden wegen Viren übernommen. Auch wird keine Haftung 
für Schäden übernommen, die aus einer Veränderung des Inhalts dieser Nachricht 
durch Dritte entstehen können. Wenn Sie auf diese Nachricht antworten, beachten 
Sie bitte, dass durch innerbetriebliche Regelungen Ihre E-Mail eventuell auch 
durch einen anderen als den bezeichneten Adressaten gelesen werden kann.
This message is confidential and intended solely for the use of the individual 
or organization to whom it is addressed. Should you not be the intended 
addressee of this message or his or her representative, please note that 
publication, replication of the contents by any means or further communication 
of the content is not permissible. Should you have received this message in 
error, please notify the sender. This message was scanned by a virus and 
content filter but liability for any viruses transmitted will not be accepted. 
Furthermore we are not liable for damages arising from alteration of the 
contents of this message by a third party. If you reply to this message please 
keep in mind that due to innerorganizational regulations your message could 
probably be read by someone else than the intended addressee.
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Selecting variant automatically - if only one is available

2012-07-31 Thread Marat Bedoev 
Hello,

you may override the function getProduct() used for rendering details page.
http://docu.oxid-esales.com/CE/sourcecodedocumentation/4.6.2.46646/details_8php_source.html#l00735

there you can check if the article has only one variant (not sure if it does 
really make sense to have a not buyable parent article with one single variant) 
or what ever you want and then load the article/variant you want

kind regards
Marat

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Gregor Walter
Gesendet: Dienstag, 31. Juli 2012 11:38
An: dev-general@lists.oxidforge.org
Betreff: [oxid-dev-general] Selecting variant automatically - if only one is 
available

Hey there,

I am struggling a bit with automatically selecting one available variant 
automatically. Either because there is only one variant (child) for that 
parent, or only one is "available" (all other sold out).
Doing it with Javascript is a bit awkward, as it would have to reload the page 
right away after loading it..

thanks for your ideas
Gregor




Der Inhalt dieser Nachricht ist ausschlie?lich f?r den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Nachricht oder dessen 
Vertreter sein sollten, so beachten Sie bitte, dass jede Form der 
Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser Nachricht 
unzul?ssig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der 
Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch einen 
Virenscanner auf Viren und sonstigen sch?dlichen Inhalt gepr?ft, jedoch wird 
keinerlei Haftung f?r Sch?den wegen Viren ?bernommen. Auch wird keine Haftung 
f?r Sch?den ?bernommen, die aus einer Ver?nderung des Inhalts dieser Nachricht 
durch Dritte entstehen k?nnen. Wenn Sie auf diese Nachricht antworten, beachten 
Sie bitte, dass durch innerbetriebliche Regelungen Ihre E-Mail eventuell auch 
durch einen anderen als den bezeichneten Adressaten gelesen werden kann.
This message is confidential and intended solely for the use of the individual 
or organization to whom it is addressed. Should you not be the intended 
addressee of this message or his or her representative, please note that 
publication, replication of the contents by any means or further communication 
of the content is not permissible. Should you have received this message in 
error, please notify the sender. This message was scanned by a virus and 
content filter but liability for any viruses transmitted will not be accepted. 
Furthermore we are not liable for damages arising from alteration of the 
contents of this message by a third party. If you reply to this message please 
keep in mind that due to innerorganizational regulations your message could 
probably be read by someone else than the intended addressee.
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Metadata: Problems on registering multiple entries for one class

2012-06-28 Thread Marat Bedoev 
Hello,

in case if your module does not extend an OXID class but adds a custom class, 
you can extend your custom class to get menu.xml workin.
like this:

metadata.php -
….
'files' => array(
'myClass' => 'myModule/myClass.php',
),
'extend'=> array(
  myClass' => 'myModule/myClass-ext',
),

myClass-ext.php ---
class myClass-ext extends myClass-ext_parent
{
public function takeOverTheWorld()
{
parent::takeOverTheWorld();
}
}

Regards,
Marat

Von: dev-general-boun...@lists.oxidforge.org 
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Björn Lange
Gesendet: Donnerstag, 28. Juni 2012 12:02
An: dev-general@lists.oxidforge.org
Betreff: Re: [oxid-dev-general] Metadata: Problems on registering multiple 
entries for one class

 Hi Kai,
2012/6/28 Kai Gazmaga 
mailto:kai.gazm...@vektordesign.de>>
this is interesting because I wrote (some) modules that extend the menue 
without having extended classes setup in modules-array - the only file in 
modules-dir is menu.xml.

Maybe this is a kind of bug - or simply new handling in 4.6. But I would like 
to see all module-dirs scanned for menue.xml without unnecessarily setting up 
files in the metadata.php.

Erik Kort said at the Unconference something like, that a module is only a 
module, if the extend array in the metadata.php is existing. And the module 
system only adds module navigations, if the module is enabled ... i would say, 
merge your module to OXID 4.6. I understand your point, but i like the way to 
"soft force" a clean api.

Regards,

Björn


Der Inhalt dieser Nachricht ist ausschließlich für den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Nachricht oder dessen 
Vertreter sein sollten, so beachten Sie bitte, dass jede Form der 
Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser Nachricht 
unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der 
Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch einen 
Virenscanner auf Viren und sonstigen schädlichen Inhalt geprüft, jedoch wird 
keinerlei Haftung für Schäden wegen Viren übernommen. Auch wird keine Haftung 
für Schäden übernommen, die aus einer Veränderung des Inhalts dieser Nachricht 
durch Dritte entstehen können. Wenn Sie auf diese Nachricht antworten, beachten 
Sie bitte, dass durch innerbetriebliche Regelungen Ihre E-Mail eventuell auch 
durch einen anderen als den bezeichneten Adressaten gelesen werden kann.
This message is confidential and intended solely for the use of the individual 
or organization to whom it is addressed. Should you not be the intended 
addressee of this message or his or her representative, please note that 
publication, replication of the contents by any means or further communication 
of the content is not permissible. Should you have received this message in 
error, please notify the sender. This message was scanned by a virus and 
content filter but liability for any viruses transmitted will not be accepted. 
Furthermore we are not liable for damages arising from alteration of the 
contents of this message by a third party. If you reply to this message please 
keep in mind that due to innerorganizational regulations your message could 
probably be read by someone else than the intended addressee.
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] Overriding admin template blocks (OXID 4.6.x)

2012-06-13 Thread Marat Bedoev 
Hello!

did somebody successfully override an admin template block in oxid 4.6?
I’m trying to override the „admin_content_main_form“ block in content_main.tpl. 
Got the block record into the oxtplblocks table, but can’t make it work.
Have already tried lots of different combinations of template names and patches 
like „out/admin/tpl/content_main.tpl“ or just „content_main.tpl“ and everything 
„between“.

Thanks a lot and best regards
Marat // vanilla thunder


Der Inhalt dieser Nachricht ist ausschließlich für den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Nachricht oder dessen 
Vertreter sein sollten, so beachten Sie bitte, dass jede Form der 
Veröffentlichung, Vervielfältigung oder Weitergabe des Inhalts dieser Nachricht 
unzulässig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der 
Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch einen 
Virenscanner auf Viren und sonstigen schädlichen Inhalt geprüft, jedoch wird 
keinerlei Haftung für Schäden wegen Viren übernommen. Auch wird keine Haftung 
für Schäden übernommen, die aus einer Veränderung des Inhalts dieser Nachricht 
durch Dritte entstehen können. Wenn Sie auf diese Nachricht antworten, beachten 
Sie bitte, dass durch innerbetriebliche Regelungen Ihre E-Mail eventuell auch 
durch einen anderen als den bezeichneten Adressaten gelesen werden kann.
This message is confidential and intended solely for the use of the individual 
or organization to whom it is addressed. Should you not be the intended 
addressee of this message or his or her representative, please note that 
publication, replication of the contents by any means or further communication 
of the content is not permissible. Should you have received this message in 
error, please notify the sender. This message was scanned by a virus and 
content filter but liability for any viruses transmitted will not be accepted. 
Furthermore we are not liable for damages arising from alteration of the 
contents of this message by a third party. If you reply to this message please 
keep in mind that due to innerorganizational regulations your message could 
probably be read by someone else than the intended addressee.
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general

[oxid-dev-general] jQuery in Backend

2012-01-30 Thread Marat Bedoev 
Hello!

How would you feel about replacing the default backend's JavaScript by jQuery?

In the face of coming backend changes like oxblocks for providing a simplier 
way of customizing and extending the backend, it makes some sense of using 
jQuery in the backend as well as in frontend.



However, i would be happy :)




Many greetings from germany
Marat Bedoev

[cid:image001.jpg@01CCDF3D.15A696E0]
HEINER DIRECT GmbH & Co. KG
Auguststr. 1
53229 Bonn

eMail   marat.bed...@heiner-direct.com<mailto:marat.bed...@heiner-direct.com>
web www.heiner-direct.com<http://www.heiner-direct.com/>




Der Inhalt dieser Nachricht ist ausschlie?lich f?r den bezeichneten Adressaten 
bestimmt. Wenn Sie nicht der vorgesehene Adressat dieser Nachricht oder dessen 
Vertreter sein sollten, so beachten Sie bitte, dass jede Form der 
Ver?ffentlichung, Vervielf?ltigung oder Weitergabe des Inhalts dieser Nachricht 
unzul?ssig ist. Wir bitten Sie, sich in diesem Fall mit dem Absender der 
Nachricht in Verbindung zu setzen. Diese Nachricht wurde durch einen 
Virenscanner auf Viren und sonstigen sch?dlichen Inhalt gepr?ft, jedoch wird 
keinerlei Haftung f?r Sch?den wegen Viren ?bernommen. Auch wird keine Haftung 
f?r Sch?den ?bernommen, die aus einer Ver?nderung des Inhalts dieser Nachricht 
durch Dritte entstehen k?nnen. Wenn Sie auf diese Nachricht antworten, beachten 
Sie bitte, dass durch innerbetriebliche Regelungen Ihre E-Mail eventuell auch 
durch einen anderen als den bezeichneten Adressaten gelesen werden kann.
This message is confidential and intended solely for the use of the individual 
or organization to whom it is addressed. Should you not be the intended 
addressee of this message or his or her representative, please note that 
publication, replication of the contents by any means or further communication 
of the content is not permissible. Should you have received this message in 
error, please notify the sender. This message was scanned by a virus and 
content filter but liability for any viruses transmitted will not be accepted. 
Furthermore we are not liable for damages arising from alteration of the 
contents of this message by a third party. If you reply to this message please 
keep in mind that due to innerorganizational regulations your message could 
probably be read by someone else than the intended addressee.
<>___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general