That's great news!
Thanks Dan.

On Tuesday, 19 January 2016 17:52:45 UTC+2, Dan wrote:
>
> I can do that. Actually, I have almost everything ready. There's only 
> three modules I haven't "finished", and they just need a bit of polishing 
> as I have them working elsewhere.
>
>      Notify -- being notified when pages are edited.
>      Inbox -- part of the ez-news script for processing bounces.
>      Store -- our ecommerce system using Simplify (like stripe).
>
> I wanted to get the Store up and running to handle payments for the XPack, 
> but there's no reason I can't use PayPal now and release the modules I 
> have...
>
> I'll try and get to it next week. I should add there may be a period of 
> debugging and ironing stuff out as we try and get everything perfect. But 
> that's easier if we have a few others looking at the code. And we're pretty 
> close as I'm intentionally using core XPack features everywhere possible on 
> the BoltWire site.
>
> Thanks for sharing our software with your company! Give me a week...
>
> Cheers,
> Dan
>
>
>
> On Tue, Jan 19, 2016 at 1:23 AM TMurNGon <tmur...@gmail.com <javascript:>> 
> wrote:
>
>> Thanks for that Dan.
>>
>> Just asking:  Any chance of you releasing just a partial expansion pack 
>> (just the bits that are complete to date)?
>> I'm trying to convince the 'powers that be' to change to Boltwire for our 
>> company intranet and some (most) of those components would be very welcome.
>>
>> Just saying ;-)
>>
>> Thanks.
>> Jan
>>
>>
>> On Tuesday, 19 January 2016 04:23:41 UTC+2, Dan wrote:
>>>
>>> Despite my initial desire to have the expansion pack out by the first of 
>>> the year--I made the strategic decision to focus on a couple other projects 
>>> first. And I don't see any good openings in my calendar for the next few 
>>> months at least. 
>>>
>>> There is not a lot left to do--just really having fun with my other 
>>> projects, and wanting to program a bit less and enjoy life a bit more! :)
>>>
>>> I did just release another version of BoltWire with lot's of nice fixes 
>>> and improvements, but nothing dramatically different. I posted the 
>>> changelog below. If you are current, should be a good upgrade.
>>>
>>> Cheers,
>>> Dan
>>>
>>>
>>>
>>> *The Cutting Edge...**boltwire5.08.zip 
>>> <http://www.boltwire.com/downloads/go&v=5&r=08> January 18, 2016*
>>>    
>>>    - Added a myBOLTskinVar['field'] = 'value' variable so can put 
>>>    {field} in skin and insert value. Similar to code.settings page, but can 
>>>    control dynamically via php.
>>>    - Slight fix in sorting of search results when extra pages are 
>>>    included. Also can handle {+1} and {+2} in sort parameter.
>>>    - Slight fix to list function so handles no matches the same as 
>>>    search function.
>>>    - The last release introduced a new bug in the way search results 
>>>    were processed where counting took place after sorting. Fixing required 
>>>    splitting BOLTresortsWhenCount into two separate functions.
>>>    - Tweaked the set condition a bit more, so can do source=field and 
>>>    will return true if that post, get or cookie field set. Good for testing 
>>> if 
>>>    a multiline value is set that would otherwise break the markup.
>>>    - Improved BOLTfolders function so can put a site.folders page in 
>>>    the shared/pages folder.
>>>    - A couple slight improvements to the messaging controls in the 
>>>    index function.
>>>    - Slight improvements to how the type parameter in searches works. 
>>>    Now can do number/-number, and mycustom/-mycustom types, and even 
>>> override 
>>>    the default number handling by creating a custom myBOLTtypenumber 
>>> function.
>>>    - Minor tweaks in indexing. Now can do [(index rule=myrule 
>>>    batch=10)] and the batch setting will override the default value. Can 
>>> also 
>>>    do [(index 10)] and it will be the equivalent of [(index cron=10)]. And 
>>>    lastly, [(index)] will now default to the equivalent of setting the cron 
>>>    parameter to whatever your default indexBatch value is.
>>>    - Have been having problems with the auto-login process, and think I 
>>>    have fixed it at last. Like before, just use a persist=1209600 parameter 
>>> in 
>>>    the login command to keep logged in for two weeks. To get the autologin 
>>>    effect, the user must visit a page with <(login)> on it--ideally in a 
>>> zone 
>>>    wrapped in a conditional checking their login status. Change to <(login 
>>>    persist=1209600)> to extend their autologin another two weeks from that 
>>>    login date. Can also use a link like some.page&id=myid&pass=mypass to 
>>> login 
>>>    via url. This also requires <(login)> on some.page.
>>>    - Also added myBOLTlogin and myBOLTlogout hooks for those who might 
>>>    want to tweak those processes.
>>>    - Added an option $guipath variable and updated the code.embed.gui 
>>>    page. This is important for sites using add-on domains. You will need to 
>>>    update your code.embed.gui page. Contact me for information.
>>>    - Tightened the inlist conditional a bit more. Before if you did [if 
>>>    inlist some.page item] it would automatically work. It should be [if 
>>> inlist 
>>>    page=some.page item] because you might have a single item list with the 
>>>    same name as a page. It happened to me. Because this could disrupt sites 
>>>    however, I'll instead put (temporarily) page=false as a parameter to 
>>>    disable this feature and deprecate it to give you time to update to the 
>>> new 
>>>    page=some.page format.
>>>    - Very slight fix in tag function when doing a tag cloud of a page 
>>>    other than the index.tags page. Also, now should change to fmt=cloud. 
>>> Have 
>>>    deprecated just using the plain "cloud" as a parameter.
>>>    - Now list and search commands respect the if parameter properly.
>>>
>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "BoltWire" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to boltwire+u...@googlegroups.com <javascript:>.
>> To post to this group, send email to bolt...@googlegroups.com 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/boltwire.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"BoltWire" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to boltwire+unsubscr...@googlegroups.com.
To post to this group, send email to boltwire@googlegroups.com.
Visit this group at https://groups.google.com/group/boltwire.
For more options, visit https://groups.google.com/d/optout.

Reply via email to