[oxid-dev-general] Clickable logo in the module setting
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVCAlsAAoJEHNImtue0q8gXaUP/0y2zovBjFH3qIUg4UTEgVp6 zTFUmNToJ7REXi86iJ6ZUN0b8L8niJ5Zn0fyonokY9e2uvDBU10GUms3Gji63Q2A HY0f+CQKUv6G3KjnrCgEuM4KrFrfAa2t7eeqfAw0ZwhPM3rnwSyjfR2CtYSW8V5h 4rhwXRLhXMmcc9fPp0Dtk5gWwRclYV/SVlfyWnQM/ZMv/4n4UXS7CZi4/JzSRjMJ ZsC2U431iDCQ0CCsOnUZ1dvL10IebE2zpDU970XvlHhEfxaB09hhaz1sLK7wXxtR x8OtHYCcC9OwgIOpVyxsCSwQDIKqIPbxfNoxIBePWsy8BfXBjusaYHlNUz4Cf/dm K823rDLyNWfzxf4s9jyrYW0tzK6BTn9a5N4qTSRheKm7LhTIaQRg35lcyQU39TLB DOvK6Ius5xJCxOxnK9YhckXvWhOtjVrF8Fm0z5pk60YwCuJYM/gRrn6VWEegFkRW eIcLLnoPXIr5dJQs0Qdr5DChw+FkHg9SqBEEYpRxR3JFndz0YzzX2R+b+hu1Sg4s PyPq+8j7vSGiSRlPrqAagfp9Sur4Xrxpz1jt4rSfSjrOdnuHmrri/Zcwp0Rd8T6M zBxT6PiQ/aE+7sYzU0rF0RcH80AQ8N96yy6iyS5qf5Sz2Ra0zGd7d1SBSRpH/PnM SP3eYkJqN3Kv2+Ze0+WW =3QZ3 -END PGP SIGNATURE- ___ dev-general mailing list dev-general@lists.oxidforge.org http://dir.gmane.org/gmane.comp.php.oxid.general
[oxid-dev-general] Better block definition in original templates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQIcBAEBAgAGBQJVCAwEAAoJEHNImtue0q8gDusP/07o8AhSFSWRF6ktY8t1aI1L
H0k3QpYVDHn1pT5QjHPuBsOQXQpASTZubckt6uKzf4RK6xuDlg/V8voAbvsWnOLN
DZADFCPO80Q5HTfIjGr5hmQQwaCGEIOuE475Y+YVmmHWIwJimpEZqiNb+k48TmSm
WPT0YfM0zD+HMxiyQln4A59BqQaysX0Du8EKeLYpoiQfxU5px0fpZ7mrNhbH116j
Fy9EoriMM059AGac5cZPOJeDcjfIg5f6CXVGWBInjYIo6xAhDHgFBAHcdvqPQK1p
FhYfJZzfPacbZ9wgIYefUbIXOJ1EPUnnXLaRGk6NHxKd2hV6jVg0Pp4AdODW1yAr
93jxx8b1lLCNGOoUwOiai6IOQ9fEFZD29ogMF7BMWMNurZ9hGYyQCCEK4wl/ShrG
JSlvPO6rKXTuia0tc6RzdIwOFVTqrupi//rVixoL9fSaIuWdB+kPtf+c6LkybPNY
Azm+xem3NLH6+StB3ZIplZs/gfXhWZr+GsTMy3pxVhnIV/XnQb4C409lTbiQHaeh
wa/816aBsEXzFH1B0haFDDIACXBV3tNOsTKDITdVxJwa177agCV3MXeWmWiea+6y
OZ4txyeSUSLwPhb1RH8k9iwij+IqzhefV4TQl5ZkbAA+SlkOpXDhYZkByNtCC7gw
M++NWRV/+NSk7pCErswk
=Oh0w
-END PGP SIGNATURE-
___
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
Hi, there should be a provided solution for metadata-information-handling by OXID. Existing solutions with embedded HTML inside these fields (e.g. to inject a version-checker-image within title-field) aren't just a rude method, its a security-matter too. Further more, if metadata.php itself is encrypted, this may end in untrusted components, because they are executed within admin-frontend! I would suggest to change from that simple php-file to some other format, for example json, removing the possability to inject harmful code (not just browser-frontend, ist server-side-executed code too). Especially having Cross-Origin-Requests within SSL-secured context should be taken a bit more serious. greets Danny -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 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 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 -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVCAlsAAoJEHNImtue0q8gXaUP/0y2zovBjFH3qIUg4UTEgVp6 zTFUmNToJ7REXi86iJ6ZUN0b8L8niJ5Zn0fyonokY9e2uvDBU10GUms3Gji63Q2A HY0f+CQKUv6G3KjnrCgEuM4KrFrfAa2t7eeqfAw0ZwhPM3rnwSyjfR2CtYSW8V5h 4rhwXRLhXMmcc9fPp0Dtk5gWwRclYV/SVlfyWnQM/ZMv/4n4UXS7CZi4/JzSRjMJ ZsC2U431iDCQ0CCsOnUZ1dvL10IebE2zpDU970XvlHhEfxaB09hhaz1sLK7wXxtR x8OtHYCcC9OwgIOpVyxsCSwQDIKqIPbxfNoxIBePWsy8BfXBjusaYHlNUz4Cf/dm K823rDLyNWfzxf4s9jyrYW0tzK6BTn9a5N4qTSRheKm7LhTIaQRg35lcyQU39TLB DOvK6Ius5xJCxOxnK9YhckXvWhOtjVrF8Fm0z5pk60YwCuJYM/gRrn6VWEegFkRW eIcLLnoPXIr5dJQs0Qdr5DChw+FkHg9SqBEEYpRxR3JFndz0YzzX2R+b+hu1Sg4s PyPq+8j7vSGiSRlPrqAagfp9Sur4Xrxpz1jt4rSfSjrOdnuHmrri/Zcwp0Rd8T6M zBxT6PiQ/aE+7sYzU0rF0RcH80AQ8N96yy6iyS5qf5Sz2Ra0zGd7d1SBSRpH/PnM SP3eYkJqN3Kv2+Ze0+WW =3QZ3 -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] Clickable logo in the module setting
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] Better block definition in original templates
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] Better block definition in original templates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yea ...
i wouln't have problems with doing that, but wouldn't that cause
extreme BC-Breaks. There can be people that would like to prefere it
the other way around.
I would like to implement a kind of an RFC for that. Is there a way
for that in the oxid community?
greets max
Am 17.03.2015 um 12:45 schrieb 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
>
- --
- --
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
iQIcBAEBAgAGBQJVCBUgAAoJEHNImtue0q8gmT4QANlnZ+Ia8v9WYzmyYpSreoE7
QBHiL+Miy6eTz8g3+1nygYI14dCNY4Bh5DCcaTqF8EVC6/xIV61+yjne67tf2xMr
ZKMxUUoMHVZzICs3UiCTCRaPg/B9HLX94krolaZPguPG9jNSW261x0DR7DENqwYQ
X39lGedubxVou4TJzX8ePHef2yq80AQ7BXu+0O5byzbe8JBrxuKK/PvrCejdYT27
8uRl1KziuHHnDsALcJlPPvAls6nW146ktFB/25VgMah7+LRerp2EW7xl5pX8QnHv
23iZDeXZ+KhuRGDN58JZzT4YKa62O25pz0uFL5ogPhBpzkZzRqz/eaFhKMobZnko
i//rBEUSIy4YVXpmmrx0GNYO3Dxnh8IHsGZoZ4IijR6587+NkdP9HCuU8G5viceH
IbZ+8uACdx8SqyOq6NlA08rewqfod9Fhhasm1oPrGjWKMf9C/yjydUhwopJ8TEn1
ETPZ/ZoUqInORrpvlIl2wUfFW6T1l9g1YaW8wSXj7aC8GzbaudlqLWzX6+NtmfKK
L6E0tOxejs5qP1OkOO4PK19uA11gieo3nvB8cfWtk20Vz6DamapEWV6AaV0avngW
xFJfltyyrgyNNpkyezv/oCI4LUKbGnDVVCUnHi/+z8pIKM6JRt48U/SwkT1ZV8Pa
EKk97os/v7MBUHwEIHPN
=CwlD
-END PGP SIGNATURE-
___
dev-general mailing list
dev-general@lists.oxidforge.org
http://dir.gmane.org/gmane.comp.php.oxid.general
