ended recipient (or have received
this e-mail in error) please notify the sender immediately and destroy
this e-mail. Any unauthorized copying, disclosure or distribution of
the material in this e-mail is strictly forbidden.
--
Manuel Reiß
Team Lead Software Development (Berlin)
Telef
Hi Mirza,
OXID generates canonical URLs to prevent duplicate content issues. So
maybe your SEO guys should take a look at the code before coming up
with crazy ideas :)
Best,
Manuel
manuel.re...@mediaopt.de mailto:manuel.re...@mediaopt.de |
www.mediaopt.de http://www.mediaopt.de/
derksen
09
42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id
DE265886017 | geschäftsführer dipl.-ing. philipp derksen
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Manuel Reiß
Gesendet: Donnerstag, 23. Mai 2013 17:29
Hi Gernot,
to keep module-dependencies inside tpls failsafe, we're currently using
following way:
extend (e.g. oxcmp_utils) or create a component or oxViewConfig and set a
tpl-variable:
public function render()
{
//activate module for templates
//you could also add some addional checks
Hi list,
Hi Joachim,
why would you want to extend ONE class in ONE module via multiple
files? I can not imagine a situation where you can not put all your
changes into one file.
I would want this for module-patches necessary for specific OXID-versions where
some OXID-functions got wiped
Hi,
maybe you just forgot to refresh the views , which is now necessary in CE/PE
as well ?
Admin = Service = Tools = update views
Best,
Manuel
mailto:manuel.re...@mediaopt.de manuel.re...@mediaopt.de |
http://www.mediaopt.de/ www.mediaopt.de
derksen mediaopt gmbh | elbestrasse
Hi,
while playing around with the new extension-features in v4.6 Id like to
propose following enhancements in oxmodules (de-)activation handling
(already love the modulechain-handling):
· Also add template-block extensions into the metadata for an easy
(un-)install.
· Parse
[dev-general-boun...@lists.oxidforge.org] on behalf of Manuel Reiß
[manuel.re...@mediaopt.de]
Sent: Thursday, January 05, 2012 12:11 PM
To: dev-general@lists.oxidforge.org
Subject: [oxid-dev-general] Change-Request 4.6: please move delivery-address
hash to oxuser
Hi list,
at the moment Im testing
Funny to see that this bug still exists. I already described it in October
2009 in the German forum
http://www.oxid-esales.com/forum/showthread.php?t=2758
mailto:manuel.re...@mediaopt.de manuel.re...@mediaopt.de |
http://www.mediaopt.de/ www.mediaopt.de
derksen mediaopt gmbh |
Hi,
i would also prefer a different handling for text-fields since it also
boosts up the database if you have a sh**load of variants where most fields
are not needed.
Regarding internationalization (i18n) you could store all multilang fields
in a separate table (e.g. oxarticles__i18n) with a
Hi,
what may be of interest for your issues is, that there's a wierd behavior with
OXID dealing request-parameters accessed via oxconfig::getParameter().
OXID either takes Get-parameters or Post - mixing is not possible. You can see
it in oxconfig's getParameter() method:
...
if ( isset(
marketing stuff - take a look at the queries if you wanna send flowers to
your female customers only ;) ).
my 2 cents...
Manuel Reiß
-Ursprüngliche Nachricht-
Von: dev-general-boun...@lists.oxidforge.org
[mailto:dev-general-boun...@lists.oxidforge.org] Im Auftrag von Tomas
Liubinas
12 matches
Mail list logo
