Hmmm... I'm getting some weird behavior too. Sometimes. Not always.
Looking into it a bit, it seems the information is getting mangled
somehow before it gets to the info function. Possibly in the comm2func
connector. I'll look into it, and try to post a fix later. It's not
you--seems to be the core code.
Cheers,
Dan
P.S. Ok, here's the fix--I think... In comm2func, engine.php ~452
change it to include this str_replace fix:
foreach($args as $f => $v) $value .= "$f='" .
str_replace(Array("'",
'"'), Array(''', '"'), $v) . "' ";
The problem has to do with the apostrophes not getting escaped and
therefore causing problems in the BOLTargs parameterization.
The other thing, is the info commands in the action.skin form need to
have ' ' to protect their values from spaces. Particularly
[session info_1 "target=code.snippets field=sitename value='{=sitename}'"]
[session info_2 "target=code.snippets field=slogan value='{=slogan}'"]
[session info_3 "target=code.snippets field=description value='{=description}'"]
[session info_4 "target=code.snippets field=keywords value='{=keywords}'"]
[session info_5 "target=code.snippets field=webmaster value='{=webmaster}'"]
[session info_6 "target=code.snippets field=sidebar value='{=sidebar}'"]
[session info_7 "target=code.snippets field=accent_color
value='{=accent_color}'"]
[session info_8 "target=code.snippets field=background_color
value='{=background_color}'"]
[session info_9 "target=code.snippets field=text_color value='{=text_color}'"]
[session info_10 "target=code.snippets field=box_color value='{=box_color}'"]
Remember to change the core system function rather than editing it
through the browser as it is likely there will be additional tweaks to
the skin/form until we get it right. Thanks for spotting this!
Actually this is even smarter, hey?
[session target code.snippets]
[session info_1 "field=sitename value='{=sitename}'"]
[session info_2 "field=slogan value='{=slogan}'"]
[session info_3 "field=description value='{=description}'"]
[session info_4 "field=keywords value='{=keywords}'"]
[session info_5 "field=webmaster value='{=webmaster}'"]
[session info_6 "field=sidebar value='{=sidebar}'"]
[session info_7 "field=accent_color value='{=accent_color}'"]
[session info_8 "field=background_color value='{=background_color}'"]
[session info_9 "field=text_color value='{=text_color}'"]
[session info_10 "field=box_color value='{=box_color}'"]
On Mon, Sep 21, 2009 at 4:10 AM, DrunkenMonk <[email protected]> wrote:
>
> Could you post the source you are using?
>
> On Sep 21, 6:58 am, Dustin <[email protected]> wrote:
>> And if I leave the field empty and click save, it changes to a value
>> of "value=".
>>
>> -dustin
>>
>> On Sep 20, 11:56 pm, Dustin <[email protected]> wrote:
>>
>> > Not sure if this is a 3.15 issue, or a generic issue, but I'm having
>> > trouble changing the form values on the action.skin page. Namely, I
>> > can't put spaces in any of the text fields. If I do, when I click
>> > submit, they revert to the previous value.
>>
>> > -dustin
>>
>> > On Sep 20, 5:51 am, The Editor <[email protected]> wrote:
>>
>> > > Just released 3.15 with a couple minor fixes--one of which caused me
>> > > tons of grief, essentially crashing all my sites, so it might be worth
>> > > upgrading! :)
>>
>> > > I reworked the site.index page quite nicely. Try it out on a new
>> > > install. You'll like it. Also, you can now add searchLimit: 25 in your
>> > > site.config page and you won't have to worry about searches timing out
>> > > because you have hundreds or thousands of hits. Unless you
>> > > deliberately tell it to return hundreds or thousands of hits... :)
>> > > Should be helpful for new users.
>>
>> > > From the changelog:
>>
>> > > * Added the _ to the parameter filter list.
>> > > * Fixed a small bug in the links:urls markup rule, that caused me big
>> > > problems! :)
>> > > * Minor change to index function and major reworking of site.index
>> > > page to make easier to use, and to incorporate features of
>> > > action.index, now deleted.
>> > > * Added an optional searchLimit config var that limits hits to some
>> > > number unless specified otherwise in the search function. The default
>> > > core setting is now 25.
>> > > * Removed several antiquated entries from the core site.config page.
>>
>> > > Glad to report the BoltWire is now up and running efficiently once again.
>>
>> > > Cheers,
>> > > Dan
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/boltwire?hl=en
-~----------~----~----~----~------~----~------~--~---
