t;
> --
> Kevin Reed
> TNET Services Inc.
>
> On Wed, Aug 10, 2016 at 8:35 AM, The Editor <fast4...@gmail.com> wrote:
>
>> Yes, this is a bit problematic. We can't update to anything past php 5.5
>> without changing the preg_replace functions, and as soon as we u
Yes, this is a bit problematic. We can't update to anything past php 5.5
without changing the preg_replace functions, and as soon as we update them
anything below php 5.2 gets invalidated. I think we are best to move
forward as the php changes are security related, and its something we need
to do
Not sure why you had problems with the { 2+3 }. It is working here on this
test page:
http://www.boltwire.com/test/math
Nice use of the math function combined with a search query. Very clever...
Cheers,
Dan
On Sat, Aug 6, 2016 at 5:51 AM mz wrote:
> Thank you Dan for
Yes, I still plan to go through and separate the two back out again. It
won't really affect things particularly for users, but just makes
management on my end a lot easier. No idea as to the time table however.
Everything is working pretty good at the moment and I'm swamped with
projects so my
I don't think just setting ssl to true is enough. It just takes care of
certain things within BoltWire. I have the following lines in my index.php
script and it seems to do the trick, without requiring me to make any
changes to my .htaccess files. (They do have settings required for
cleanURL's of
Can you give me an example where this does not work? For example, if I do
[(math 10/3)] I get 3.33. If I change it to [(math 10/3 decimal=4)] then I
get 3..
It seems to be working, but maybe you are doing something in a different
context...
Cheers,
Dan
On Sun, Jul 31, 2016 at 12:51 PM mz
Hi Matt,
This is a little strange. I've checked all my sites and they seem to be
working fine.
Can you tell me what version of php you are using? We trying to transition
from 5.4 to 5.5 and are having some issues. This could possibly be related.
I'm assuming you are using the latest version of
the next hour or so.
Cheers,
Dan
On Fri, May 27, 2016 at 1:03 PM erik burggraaf <burggraafe...@gmail.com>
wrote:
> Hi Dan,
>
> FTP access is as follows.
>
> ftp.erik-burggraaf.com
> port 21
> username boltwire
> password acCesS42
>
> Thanks for looking.
>
>
Just released a new version of BoltWire--that marks a pretty important
milestone. Namely, I've upgraded code throughout the entire script to bring
BoltWire into line with PHP 5.5 and above. Unfortunately, this release will
probably break sites relying on PHP versons below 5.3, but there just
The field can only include letters, numbers, or a hyphen or underscore.
Cheers,
Dan
On Fri, May 20, 2016 at 9:39 PM erik burggraaf
wrote:
> Hello, I'm trying boltwire for the first time on my linux web hosting
> package. I uploaded the boltwire package and set my
Can you tell me which page you saw that on? That feature was discontinued
some time back.
It would probably be easy enough to do however. You add a javascript
snippet to code.js that handles the form submission and then add the
appropriate js parameter to the third part of any regular link. I'm
Maybe, but my inclination is to leave it open so developers can set it up
if and how they want. If there's a demand/need for this it could always be
added...
Cheers,
Dan
On Tue, Apr 19, 2016 at 6:58 PM TMurNGon wrote:
> Just a thought: How about making this a permanent /
Looks like you're right. Will fix that in the next release. Sorry for the
confusion! Appreciate you catching this!
Cheers,
Dan
On Tue, Apr 19, 2016 at 6:01 PM TMurNGon wrote:
> Tried it and it works ;)
>
> The only problem I came across was (I think...) a typo in the hook
Sure very easy to save that skin as a data variable on the page and have
your config file do something like:
$BOLTskin = BOLTinit($BOLTskin, BOLTvars("$pageLink:skin"));
Didn't test, but this basically changes the skin if the page var for skin
on a page is set. Unfortunately this won't offer
Are you actually going p=book.one=view?
The view action won't be called unless you use the action parameter to call
it. Otherwise just the regular page will load.
Cheers,
Dan
On Thu, Apr 7, 2016 at 11:50 AM 'DIG Germering' via BoltWire <
boltwire@googlegroups.com> wrote:
> I am just learning
facebook and twitter
feeds, access an AlexaEchoes googlegroup page, etc. It also has tools for
embedding tweets, youtube, etc. I may also harness my little image editor
to automatically resize blog photos. Using this approach makes setting up a
blog almost effortless.
In fact, I like this blog so
Hi Jan!
Martin is correct. PHP is the best way to set the skin dynamically. It is
difficult to set the skin using information in the page, because the skin
is set before the page is loaded and its variables read. But if the
approach above doesn't work, I'm sure we can concoct something easily
It uses the default skin included in the Expansion Pack. It is based on a
simplified version of the bootstrap framework developed by twitter.
It's pretty easy though to take any open source skin and convert it to a
BoltWire skin. I wish we had a few developers here to take an interest in
that and
That's part of the top zone. You can edit page top and wrap the {actions}
inside a print conditional, like: [if ! print]{actions}[if]. Probably
should remove them from the default skin...
Cheers,
Dan
On Fri, Feb 26, 2016 at 9:19 AM 'Brian Platt' via BoltWire <
boltwire@googlegroups.com> wrote:
Just released version 5.10 with the corresponding XPack. To keep things
simpler, I've decided to give the XPack the same release number as the core
scripts, and in the future plan to release both simultaneously each
release. I'll also try to incorporate notes about both versions in the
changelog.
Ok, I think I have a solution for you...
First, you are correct, you must use mypage*. The auth pages do not
recognize the mypage.* syntax. That's just in searches.
Second, I doublechecked your code modification to the BOLTloadpage
function, and discovered the problem is not there at all, as it
So to clarify, what happens with the various scenarios:
view permission, but not invite permission?
invite permission, but not view permission?
both view and invite permission?
neither view or invite permission?
This might help narrow down where the problem is... Also are you using
groups
ybe delete action.zones from the core. Yours
>>>> perhaps could be a merger of the zones and data action, and if so we could
>>>> make the info vars editable fields like the data action. I'm thinking a one
>>>> stop action page for setting everything on a page...
Would it work to just change it to [[{field}|{sitename}]]. That should let
BoltWire resolve the link to the right place.
In my preliminary tests, it seems to work ok. :) Happy to make this change
to the default distribution.
Cheers,
Dan
On Mon, Feb 15, 2016 at 12:53 AM Tiffany Grenier
be automatic. Most of my
>> indexes are specialized for specific sections. So it would be difficult or
>> impossible to have an action that works for any page. If we use the {dir}
>> approach it works perfectly if there are no site folders specified and
>> since most
How secure do you want it to be?
One solution would be to use a conditional in the header that says
something like
[if ! inpage blueteam.roster {id} && ! inlist {p}:guest_read {id}]<(forward
action.blocked)>[if]
You can then leaven the groups open to view for all logged in members, but
only
Great! Glad it worked. And I don't mind the questions. I enjoy the mental
exercise--relaxes me. And it just helps BoltWire keep getting better--which
I also like!
Cheers,
Dan
On Thu, Feb 11, 2016 at 12:52 AM TMurNGon wrote:
> Hi Dan,
>
> First off I must apologise for
Nice. A couple suggestions...
Maybe a different name might be better to avoid confusing it with the admin
module called tree. That is if we end up doing something like this in the
core/expansion pack. How about: action=page, action=pageinfo,
action=info... Just thinking out loud.
What about
I see. Sounds like a great idea. Since you are aiming this at general
users, calling it action.map makes more sense to me than action.toc.
Not sure I will add it to the core, but possibly a simplified version to go
in the XPack--mostly because of the directory problem on large sites. And
it is
I'm not sure what you are doing but in my tests it seems to be working
fine. I tried both of these:
[(search group=test341243 none='[[none|no pages]]')]
and
[(search group=test341243 template=none)]
/*
[[#none]]
[(template first)][t]
[(template each)][r][c][[{+p}]]
[(template last)][t]
Yes the problem remains because BoltWire has to scan all possible pages and
then run conditionals, types, includes/excludes, and sorting before it can
trim down to the specified count of pages. It does default to 50 hits on
the display, but it still has to scan everything unless you specify the
nce most of my folders include top level pages on down like forum,
forum.area, forum.area.timestamp, it should work for all of those. Not 100%
but a strong 99% I'd say.
Kind of a cool development...
Cheers,
Dan
On Thu, Feb 11, 2016 at 11:58 AM The Editor <fast4...@gmail.com> wrote:
> Yes th
1) First a quick question about something I didn't get about your form: Why
the single [box] input? Did you omit part of the form when you posted it?
Or just something you neglected to delete?
2) From the error message, you can see that the {=upload} replacement var
is not being populated. From
Correct, $cryptkey. Sorry about that.
On Tue, Feb 9, 2016 at 12:10 AM TMurNGon wrote:
> Thanks that worked.
> It would seem though that it should be:
> $cryptkey = 'randomvalue';
> not
> $BOLTcrypt = 'randomvalue';
>
>
>
> On Monday, 8 February 2016 15:51:20 UTC+2, Dan
Try putting [messages] on the page and see what error message your are
getting. I've looked at the code and it does seem to allow multiple dots in
the new upload page name. Haven't run a test scenario though.
Another suggestion might be to try using a hyphen or underscore instead of
the dot. But
It should just be [^filename.pdf label='download'^]. Add dir=docs if it is
in files/docs.
On Mon, Feb 8, 2016 at 3:37 AM TMurNGon wrote:
> Hi Dan,
>
> I am trying to create an 'attachments' section for some pages.
> The uploading of files works well, but I can't quite figure
When you create the site (using start.php), you have the option to add
encryption or not.
To turn it on, you set $BOLTcrypt = 'randomvalue'; in index.php before
calling BoltWire. This will invalidate all your existing password. You
could conceivably write a custom script to encrypt all your
Yes, the header markup only works when it is at the beginning of a line.
That is, BoltWire looks for \n! to trigger the tag.
I took a look at the comment template(s) and it turned out to be pretty
easy to fix:
Go to your xpack system pages and look for blog.template.comments and also
This looks great Edward. Of course for the English I would recommend just
pointing them to the BoltWire site itself, as that will most likely
maintain the most current and complete information. I've personally found
keeping docs in multiple locations in sync even harder than keeping them
current!
Try a form with this command:
[command info delete page=... field=...]
On Fri, Feb 5, 2016 at 6:49 AM TMurNGon wrote:
> Hi Dan,
>
> Learning from your 'comments' implementation I have been able to add other
> data items such as 'links' etc to a page and it works very well.
All kinds of possibilities. What I did that worked great for me was to add
a line like this in my config.php script:
$sessId = strtolower(session_id());
$BOLTvar['sessid'] = $sessId;
Then I could easily store whatever info I wanted on an info page and
retrieve it using {sessid}. For example
I have looked at the code and did more testing and you are right. BoltWire
uses a simpler and faster algorithm than the search function and does not
recognize the "." in c. Only whole page parst and the "*" symbol.
Given what you are trying to do, one approach might be to create an action
like
Thanks Jan. You are right. I'l fix that for the next release. :)
Cheers,
Dan
On Tue, Feb 2, 2016 at 2:37 AM TMurNGon wrote:
> Hi Dan,
>
> Just checking if this is intended behaviour:
>
> In code.skin.bootstrap.html you set 'actions' to only be visible to admin.
> I assume
Yes this is fine. Please see my note about setting it in config.php. You
can use the BOLTinfoPeek function to extract the language setting.
As for garbage collection, set each var to ip: lang | timestamp
Then periodically delete values that are older than a certain time. To
retrieve you use
Ok. You cannot do {{=rule}_time} because of the order of processing. The
outside variable is processed at the time the page is loaded. The {=rule}
replacement variable is not processed until after the form is submitted. :)
Glad you are enjoying BoltWire. Feel free to post a link to show some of
t;>
>>>>
>>>> On Monday, 1 February 2016 15:08:25 UTC+2, Dan wrote:
>>>>>
>>>>> PS. Just updated the docs. Anytime I post something like this in the
>>>>> forum--please either copy it to the docs or remind me too, because I
>&g
Yes. You can even have grand children folders. Let say you have a large
site and want to search the forum quickly. On the BoltWire site for example
I have on page site.folders:
forum: community/forum
Then on my server I have a directory structure like
pages
community
forum
You may have to get a MAC person to help with this, but here's basically
what's happening:
BoltWire is checking to see if it can find the image and is reporting that
it is there (using the relative path). But when it tries to create the link
(using the absolute url) it is not able to do it
PS. Just updated the docs. Anytime I post something like this in the
forum--please either copy it to the docs or remind me too, because I
typically forget! :)
On Mon, Feb 1, 2016 at 6:59 AM The Editor <fast4...@gmail.com> wrote:
> Yes. You can even have grand children folders. Let say
Ah, you are a jewel Tiffany. Definitely appreciate all your help making
BoltWire better!
Since the core setup uses the default site.index.cron this shouldn't affect
too many users. And I don't see much merit to indexCron vs cronIndex except
we have indexBatch, indexInclude, indexExclude, etc. So
Ok. Still, thanks for catching the inconsistency. Every little bit helps!
Cheers,
Dan
On Mon, Feb 1, 2016 at 10:08 AM Tiffany Grenier
wrote:
> I just noticed I made a typo in "indexing: cron", so the reason why it
> wasn't working for me (not even writing in
That's the option I ended up going with. :) The XPack is a full install
package. You can dump the contents over your existing boltwire install or
extract as a separate directory and then point sites to either boltwire or
xpack. The scripts are the same in the both, and only a few of the core
Ok, you have done more than enough to help with debugging! I just manually
created your account and will send you a new password. You should be able
to change it to whatever you want once you are logged in.
I'll keep checking into it why the email didn't get to you--it could just
be spam filters
The images problem is quite tricky and it may be the solution I tried in
the last release does not work in some situations depending on server
configuration.
A couple questions:
Is it your localhost or web server and what kind of server? If a webserver,
can you send me a link to peek at?
When
Ok, here's my other issue--though I think I may have solved it...
Images
I've been having problems with them for a long time, in particular with
addon domains. Didn't know how to check if an image existed in your xpack
directory if you were using an addon directory and the xpack library was
I had a few more problems than I anticipated with the release of the XPack
as I want to make sure it is as close to rock solid as possible--and a
couple things have been giving me fits. Thought I would throw them out
there and solicit some feedback. I'll post one below and the other in a
second
Hi Everyone!
Just wanted to send out a quick memo to let you know I just released
version 5.09 of BoltWire, with several fixes and changes. And at the same
time, I released XPack 1.00.
You can read the changelog at www.boltwire.com.
To get the XPack, go to
No problems. Happy to answer as I have time...
Where do you have this markup? If it is in the header than most likely it
will not work because the header and footer is turned off by default when
an action is called. When you put it on the page, you will only see the
variable when the page content
I've just made a few updates to the BoltWire site -- namely I've created a
docs group that gives members in that group access to editing the docs
pages. And I've added a few members to that group.
You can tell you are in this group if you see an (EDIT) link in the header
of the doc page.
I also
You should be able to do
Total Pages: [(counter 0 id=total start='{(search group=docs* fmt=count
count=false)}')]
And then wherever you need that number use <(counter 0 id=total)>
Cheers,
Dan
On Tue, Jan 26, 2016 at 11:18 PM TMurNGon wrote:
> Hi Dan,
>
> The reason I did
Yes, this is a good idea. In the XPack there is a tree module which allows
you to copy, rename, and delete whole trees very easily (plus more). We
could incorporate some of that code in the core but I'm inclined to think
it is might be better staying as a plugin. I'll make a note and look at how
Could you just do
Total Pages: <(search group=docs* fmt=count count=false)>
As for your question, though, if you change fmt to template it should work.
With fmt, the output is returned unprocessed--so the counter function is
not triggered within the search function. And since the output is
Thank you! Will fix that for the next release.
On Tue, Jan 26, 2016 at 11:35 AM Tiffany Grenier
wrote:
> Hi,
> Noticed a bug in 5.08 (and previous versions), with the count=start-end
> syntax cmbined with a when parametrer.
> In BOLTsearchResultWhen, if ($count && $i
I'm going to consider this a bug and change the default number type to
check for numbers and not just that the page is numeric. This could break
some sites if you are relying on this feature though I don't believe the
documents claim this. If anyone has a concern I can deprecate for a release
or
Hi Edward,
So sorry for the inconvenience. Trying to get all the settings just right
can be a bit tricky. In this case I had the email authorization off for the
page. Just tried it and the email came right to me.
Give it a shot and let me know if you have any further problems. Appreciate
your
The number type is a special case rule and it doesn't work with a list like
you have given. Either you check for a number/-number or you check for a
list of types/-list of types.
To do what you want, you have two options--
1) Create a custom type rule which does what you want. More trouble but
Sorry about that. Looks like we had a permissions problem. Something broken
in one of our recent upgrades.
Give it another try and if you still have problems let me know. Sorry for
the inconvenience!
Cheers,
Dan
On Mon, Jan 18, 2016 at 5:11 PM wrote:
> Hello Dan,
> I
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
As you probably noticed, the tags function does not work like a typical
search function so implementing this was not trivial. But it is a great
idea and with a little thought I was able to take a stab at it. Here's the
rewritten tags function allowing you to use a when parameter.
function
Glad you got your query to work! As for your questions...
The inlist conditional currently only works with comma separated values.
But spaces before and/or after the commas are trimmed out. I can see the
merit in extending it however, as it would allow you to import csv files
with tab or space
Not sure I get the question, but could you do something like:
#1
[(search query=index.site when='! set {index.tags::{+p}} && ! set
{index.tags::{+p}:parent}' count=...)]
#2
[(search query=index.tags when='inlist {index.tags::{+p}::1} {?plot} &&
inlist {index.tags::{+p}:parent::1} {?plot}'
Great. I just update the docs. :)
On Wed, Jan 13, 2016 at 2:06 AM Tiffany Grenier
wrote:
> Hi Dan,
> I thin I'll go for the variable, in order to ensure consistency between
> indexing and reading indexes.
> BoltWire offers so many possibilities, it's so easy to forget
Ok, just did a quick update.
On Mon, Jan 11, 2016 at 11:52 AM Tiffany Grenier
wrote:
> Hi Dan,
>
> I can't seem to be able to find the "tags" function documentation page on
> the website. It would be a nice thing to add next time you plan on writing
> some doc,
Ok, I understand what you are saying now. And I note I didn't answer your
question, either...
So here's the general way indexing is supposed to work as I remember it:
1) If you set indexing to cron in site.config, changed pages get logged on
page site.index.cron--and the pages are NOT indexed.
It's no problem. Anything we can do to improve BoltWire according to our
core principles is welcome. And your suggestions are always helpful.
If we do some refactoring of the search and list features, it will only be
shuffling code around about. Not really adding or removing anything. So it
Ah legends...
Ok, let me see if I can figure out how this works...
1) A legend is used to convert email to #3 or whatever part it is in the
info line. So in query searches email(=)s...@email.com is basically a short
converted to #3(=)s...@email.com
2) The legend is found by searching for
a)
I'm not sure I see the problem, or else I have already fixed it for the
next release (possible). I'm doing this and it works perfectly:
[(search group=test* count={?start}-{ {?start}+3 })]
If start is not defined it gives me the last item only which is not really
a bug so much as a quirk, as
I tried a different approach that seems simpler to me. I basically rewrote
the following section of the BOLTsearchResults function:
if ($args['type'] == '') $args['type'] = BOLTconfig('searchType');
else {
$type = strtolower(BOLTutf2url($args['type']));
if (substr($type, 0, 1) == '-') {
$type =
Hi Martin,
I have not done a great job updating the docs with all the new features in
BoltWire. Keep meaning to go back through all the changelogs, but have not
been able to find the time. If you or anyone on the list would like to
help, let me know and I can open up edit permissions. Maybe
As a small token of my appreciation to everyone who has helped BoltWire
make some pretty big advances this year, and just to show a bit of
Christmas cheer--I'm happy to release version 5.07. It's one whopper of a
Christmas present.
8 Bug Fixes
10 New Features (mostly small)
9 Improvements to Code
I've pretty much got the XPack setup and working on my home computer. Just
have a few more days work to get it more bullet proof, polished, and
debugged. I have the BoltWire site running on what will be version 5.07 and
xpack 1.0 right now...
To get a look at the feature set, please visit the
Thank you for your support of BoltWire, Martin. You have been a big part of
the progress we made this year.
Here's to 2016!
Cheers,
Dan
PS. I fixed the DNS problem. May take a couple days to propagate. Go to
www.boltwire.com to avoid the message.
On Thu, Nov 26, 2015 at 11:34 AM mz
Thanks for the kind thoughts, Jacmgr! Kids are all grown and away from
home, but do plan to take some time with the wife as well. May sound
strange--but working on BoltWire is actually quite refreshing. If I did
programming all the time, I'm sure I wouldn't feel the same. But since it
is more a
Reposted from the BoltWire Blog...
Getting emails to work right is a huge hassle. The BoltWire XPack will make
it easier...
If you haven't worked much with emails, and email newsletters in
particular, it's a headache. The prevalence of spam has forced email
providers to start clamping down on
I've just written a new function I'm considering adding to the core -- just
wondering if it would be of use to anyone. It's a pretty versatile prev /
next function you can easily add to a header to generate the suggested
links. It's formattable, fast, easy to use.
If there's not much interest I
Reposted from the BoltWire Blog...
Looking forward to a much needed vacation in December. Will it include time
for a holiday Xpack release?
As those who follow the development of BoltWire know, we have been
promising an Expansion Pack for sometime. But as BoltWire is a volunteer
project, it gets
No problem, happy to help. I just added some documentation about this on
the special vars page.
Cheers,
Dan
On Sun, Nov 8, 2015 at 5:22 AM Tiffany Grenier
wrote:
> Great eyes!
> You are a genius. Never would have thought of that!
> So anyway, for whoever might be
The when parameter does a lot more processing than the type parameter which
simply looks at page names. So making the type function more powerful is a
great idea. Exactly the kind of think I like to do with BoltWire. All for
it!
But I can't quite comprehend the notation for the code changes you
When I first tried this, my code worked fine. Couldn't figure out what you
were saying, until I noticed you have spaces in your math expression.
So { {+matches} - 2 } needs to be { {+matches}-2 }
Otherwise the - and 2 are ignored (considered separate parameters), and it
returns the value of
I would consider this a bug, but a strange one. I copied your exact code to
test.nicepage, and set the data var, and I got completely different
output--exactly what it is supposed to be (see below). I did this both on
my local server and two different webservers. So the problem is either some
:09 AM The Editor <edi...@fast.st> wrote:
> Hi Edel,
>
> I have never really understood htaccess rewrite rules. BoltWire plays
> nice, but as for the .htaccess, all I've been able to do was hobble
> together rewrite rules from samples here and there and hope something
> works.
Hi Edel,
I have never really understood htaccess rewrite rules. BoltWire plays nice,
but as for the .htaccess, all I've been able to do was hobble together
rewrite rules from samples here and there and hope something works. :)
On my new server there is a really good tutorial that helped me
Haven't tested it, but how about using a conditional like this:
[(search query=index.tags group=danze fmt=title when="inline '{+value}'
'#emilia' && inline '{+value}' '#romagna'")]
If that doesn't work, let me know. You could replace {+value} with
{index.tags::{+p}}. Not sure all those
:)
On Wed, Oct 14, 2015 at 3:57 PM Faber wrote:
> To insert vars from the include function into the template, you have to
> change template.regioni to use {+var1} and {+var2}.
>
> This works! Thanks :)
>
> [(search query=index.tags group=danze when="inline '{+value}'
Just released version 5.05 of BoltWire. I will cut and paste the changelog
below. You can get the download here:
www.boltwire.com/index.php?p=downloads
Just for fun, I counted up the total number of releases since BoltWire 1.0
on January 2, 2008. Not counting beta's, 188 formal releases.
Just a quick note to let everyone know the BoltWire site is back up once
again. I had a bit of a problem transitioning the DNS servers properly and
ended up crashing the site for more than a day. But we're back at last. And
I have already seen amazing improvements in the new mail server, so I am
Just a note that I have initiated a move to a new server (a vps this time)
that should help improve a number of things on the BoltWire site. Until all
the DNS servers get upgraded there may be a few kinks to iron out.
If you notice anything strange the next 24 hours or so, that is the reason.
:)
Alright, just took a look at it and you only need to change your markup to
any of these:
[(tags show=cloud)]
[(tags index.tags cloud)]
[(tags cloud page=index.tags)]
etc
I'll fix it for the next release, so you can just put 'cloud' there, but as
it is currently BoltWire takes the first
On Mon, Oct 5, 2015 at 11:46 AM Tiffany Grenier
wrote:
> Hi,
>
> Thanks for reviewing all of this :-)
>
No problem. Thanks for all the great suggestions.
Concerning my use case, maybe you can find an easier way of doing it, but
> in order for you to understand what I
On Mon, Oct 5, 2015 at 2:14 PM Faber wrote:
Hi all... totally boltwire newuser here.
>
Welcome to BoltWire...
> I'm setting up a site to collect informations about european folk dances.
> Pages are grouped with "danze." prefix (i'm italian..).
> In the side zone i'm able
1 - 100 of 1686 matches
Mail list logo