Extension's ini.* files via admin interface (settings/view)

Next topic

Author	Message
Piotrek Karaś	Tuesday 18 December 2007 6:42:40 am Should admin interface make it possible to see/edit ini.* files that uniquely belong to enabled extensions? They aren't on the list in my admin... ;( Thanks, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Bartek Modzelewski	Tuesday 18 December 2007 7:21:27 am Hi Piotrek, You can simply create template with the following code: <form method="post" action={"settings/view"\|ezurl}> <select name="selectedINIFile"> <option value="your-ini-file.ini" selected="selected">your-ini-file.ini</option> </select> <input class="button" type="submit" name="ChangeINIFile" value="Select" /> </form> Should work. Bartek Baobaz http://www.baobaz.com
Piotrek Karaś	Tuesday 18 December 2007 10:18:28 am Hi Bartek, Thanks for the tip, I'll give it a try, even though I was asking about how it should behave rather than how to cope with the fact, that it does not work, if you know what I mean ;) The most difficult eZ Problems are those, that would require quite precise knowledge of many different elements, which I still try to collect... And those are most difficult to get answers to ;) Czołem, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
Heath	Tuesday 18 December 2007 4:25:45 pm Hello Piotrek, I noticed recently that in the recent move toward the future with the release of 4.0 that these features were deprecated. Re: Deprecated features in eZ Publish 4, <i>http://ez.no/developer/news/ez_publish_4_0_0_and_ez_flow_1_0_released</i> "<i>The following views have been deprecated: Global settings</i>" I took this as a positive set of subtle suggestions to developers and users as to the shift internally within eZ Publish (and eZ Components) as past code which is ... well has now been set aside for various reasons... I think this may represent an opportunity for others to create improved replacement solutions in the form of their own extensions :) Often code upon review no longer matches the current or future goals and becomes all too quickly problematic to maintain "as is" when the what would be better to do is to replace the functionality completely with a better implementation. Some of the features deprecated have already been replaced, others are Open Funding suggestions in the process of being developed or discussed. I think you can do it :) Cheers, Heath Brookins Consulting \| http://brookinsconsulting.com/ Certified \| http://auth.ez.no/certification/verify/380350 Solutions \| http://projects.ez.no/users/community/brookins_consulting eZpedia community documentation project \| http://ezpedia.org