Yes, try the section edit plugin:
http://www.boltwire.com/index.php?p=solutions.system.sedit
If the docs are not clear on how to use it let me know.
Cheers,
Dan
On Mon, May 31, 2010 at 10:24 AM, Bolti <2009addr...@googlemail.com> wrote:
> Hi all,
>
> I was wondering whether something like the
I'm away from home for a few days, and haven't had time to help with
this, but if DrunkenMonk is right, one way to change the format of the
site.language.de file may simply be to open it in BoltWire and then
resave it.
Everything in BoltWire should be UTF, but there is the possibility
something is
I'm not sure, but I think the actions are defined in code.snippets. It
depends on how your skin is set up. Are you using the default skin?
If so variables like $$actions are considered snippets. They are not
the equivalent of [(include site.actions)]... Let me know if this
doesn't help.
Cheers,
Da
s/tnet/solutions/apps/grlevel3"; >GRlevel3 App
> Data href="http://websiteaddress/tnet/solutions/apps/proftpd"; >ProFTPD
> Build href="http://websiteaddress/tnet/solutions/apps/proftpd/selfsign"; >Securing
> FTP href="http://websiteaddress/tnet/solutions/apps/
Currently I'm not collecting emails but am requiring a member account
and login. So far that has stopped virtually all spam. And this is the
first time we've had "misconduct" if that's what it was. If it
continues to be a problem, I could increase the precautions (by
requiring members to request ac
Thanks for reporting back and the summary Phoenix, I updated the
plugin on BoltWire...
Cheers,
Dan
On Sun, Apr 25, 2010 at 9:24 PM, Phoenix Wu wrote:
> It works indeed. :D
>
> a simple summary:
> original clean function in plugin infox.php
> ===
> fu
On Sun, Apr 25, 2010 at 4:10 PM, Bogdan wrote:
> On the other hand, the [option] rendering is still incorrect: value=something />label
> The correct one is: label
I think this is now fixed Bogdan. :)
Cheers,
Dan
--
You received this message because you are subscribed to the Google Groups
"B
Kevin, I think I fixed the nested divs, and the vspacing validation
issues, but I can't seem to reproduce the attachment file directory
problem. It seems to be a cleanUrl issue.
If you send me offlist a copy of your index.php file / .htaccess I
might be able to take a look. When did it break? Was
Sorry for the long delay in getting to this release. I've been busy
with another big project I'm working on, and to be honest--I was
stumped on the last few vspace problems reported. Eventually though, I
came up with some ideas for working around them, and it all now seem
to be working! Throughout
Try this:
[(include some.page basepage=true)]
Cheers,
Dan
On Fri, Apr 30, 2010 at 7:08 AM, blues wrote:
> hello everyone.
> i use a variable in a page, let's say {:title} to display its title.
> this is ok when you display the page.
> when that page is included somewhere else, the {:title} tak
Seems someone deleted a few pages. Hopefully nothing more than an
accident or a simple prank. Anyway, the pages are restored now. If we
need to, I can up the permissions again, but we've opened things
lately to encourage more user contributions...
Cheers,
Dan
On Mon, Apr 26, 2010 at 12:35 PM, c
check this... I'd
like to get this cleared up asap...
Cheers,
Dan
On Sun, Apr 25, 2010 at 4:14 PM, Kevin wrote:
>
>
> On Wed, Apr 21, 2010 at 3:12 PM, The Editor wrote:
>>
>>
>> P.S. As for #1 and the wrong path for missing marks it must be your
>> cleanURL
How about in site.config
$BOLTvar['$home'] = 'www.example.com';
And then
[[{home}|label]] or even [[{home}]]
Cheers
Dan
P.S. My goal for 4.xx will be to eliminate as many non essential
options like [[|text]] as possible, so I hate to add one now. The test
is largely 1) how often is it used and
Ok, I will make a few slight changes to the default style to have a
little more contract in color to improve readability. It will still
resemble our current style, but looking at these now repeatedly, I can
begin to see (at least some) of the problems you are talking about.
Thanks again Markus for
It definitely needs to be $p not $pp. The problem though is case
sensitivity. I set up a test installation, and found the following
slight change seems to work:
function BOLTinfoClean($info, $args, $target='') {
$before = count($info);
$exists = implode(',', BOLTsearchPageList(Array(
I'm curious if anyone else has feedback. My personal response is that
the darker link and font colors are a bit easier to read. I'm willing
to change those...
I think I prefer (personally) the grey title and blue slogan, and also
the grey sidebar secondary links, though I appreciate the goal of
ma
Yes, my guess is your code editor is not saving it with the correct
encoding. When BoltWire reads and saves it, it converts it to what it
should be. Because they are invisible to the eye, those character
encodings can be quite tricky to track down.
Glad you got it working!
Dan
On Sat, Apr 24, 20
Bogdan,
First, about the < char -- it is now no longer encoded in the source
files (if you look at the text files). Which simplifies several of
BoltWire's processes. But it is always encoded when injected into a
page to prevent malicious scripts from being hacked into your site.
If you want an if
I think it is supposed to be '\n'. Basically, if there is a line
return in the data value you get a textarea box. If not, you get a
simple text input field. Seems to be working fine for me...
Of course we could change it to a space, just I'm not sure we want a
textarea box for "Some Title"...
C
ge
> name rather than the title to provide a shorter version of the output. I
> really don't do that any longer but... thought I'd mention it.
>
> On Tue, Mar 30, 2010 at 9:28 AM, The Editor wrote:
>>
>> Ok, for next release we will have four options:
>>
Is anyone using this? I downloaded Bazaar but didn't get far in
figuring out how to use it. I'm wondering how many would be
disappointed (beside Markus) if I didn't pursue that particular
learning curve?
Cheers,
Dan
On Mon, Mar 22, 2010 at 8:33 AM, Markus Weimar
wrote:
> Hey everybody,
>
> We ha
Tue, Mar 30, 2010 at 9:44 PM, Kevin wrote:
> Sorry... the issue was different from what I thought...
>
> ->This is a
> bunch of lines
> end<-
>
> used to work.
>
> The example
>
> ->
> This is a
> bunch of lines
> end
> <-
>
> works
On Wed, Apr 21, 2010 at 6:12 PM, The Editor wrote:
> To be fully consistent we should have a reloadMark: false site.config
> option to disable the reload mark, just like the missingMark config
> option.
Oops, it's already there. If reloadMark is set to anything beside true
in sit
On Wed, Mar 31, 2010 at 11:32 PM, Kevin wrote:
> Two issues noted...
>
> 2) Reload didn't work
>
> Noted that on some sites, reload didn't work. It would not show anything
> where before it would place a ^ or in my case configured to show UP near the
> images on the page when it was used.
>
> I f
Could you add an additional (special) rewrite rule that points
www.example.com/field/index.php?p=main to www.example.com?
Cheers,
Dan
On Thu, Apr 1, 2010 at 11:05 AM, Markus Weimar
wrote:
> Hi,
>
> I am thinking of a (easy, logical, built-in) way to link to root.
>
> What about one of these?
>
This is true. Nested divs no longer work. I'll have to try and fix
them. It may be a challenge though because of how the line spacing
issue works. I'll see what I can come up with...
Thanks for everyone's patience. I've been taking a bit of a break from
BoltWire as most things finally seem to be r
On Fri, Apr 9, 2010 at 4:49 AM, Lino wrote:
>> > I like the idea of a realbackupaction and a real package action.
>>
>> I think I'm with you on this. Does anyone care to siggest the best way
>> tobackupa complete field across multiple OS's and servers, etc.
>
> I did it manually like:
> - zip-it a
On Sat, Apr 10, 2010 at 2:29 AM, Markus Weimar
wrote:
> Hey,
>
> 1) Glossary and normal links cannot be distinguished.
>
> 2) Glossary links are even inserted in links: See
> "docs.contribute.site.help.functions" at:
Ok, I'll look into these problems. Seems we made some changes to the
links funct
On Sun, Apr 11, 2010 at 9:02 AM, Markus Weimar
wrote:
> Hi,
>
> Dan, I would really like to see a comparison table on boltwire.com of
> BoltWire and PmWiki. You know, no flame war, but just pointing out the
> differences. BoltWire's story does not make it clear to me. "Radically
> different" and "
On Sun, Apr 11, 2010 at 9:30 AM, Markus Weimar
wrote:
> Hi,
>
> There is an online tool to compare a site's colors to the
> recommendations in the Web Content Accessibility Guidelines 1.0:
>
> http://www.accesskeys.org/tools/color-contrast.html
>
> It puts in numbers what my eyes have already told
This is how BoltWire handles simultaneous edits. It's designed to
protect your content when two people are editing the same page. But
you can get the same result by using multiple windows or possibly
other scenarios. So it is a feature, not a bug... :)
Cheers,
Dan
On Sun, Apr 11, 2010 at 11:58
On Sun, Apr 11, 2010 at 5:30 PM, Bogdan wrote:
> I have problem with Cyrillic text hardcoded into the code.skin. It is
> rendered incorrectly. If the text is in some page, then there is no
> problem, but if it is a part of the skin html - it is not encoded.
Do you have the right character encodin
Oh, and shouldn't that one line be
if (strpos(",$exists,", ",$pp,") === false) unset($info[$p]);
with a single $p rather than a $pp?
Cheers,
Dan
--
You received this message because you are subscribed to the Google Groups
"BoltWire" group.
To post to this group, send email to boltw...
s/info.tags";
> $fh = fopen($myFile, 'w') or die("can't open file");
> foreach ($info as $p => $v) $out .= "$p: $v\n";
> fwrite($fh, $out);
> fclose($fh);
> //
> return "
This is a good idea, but I don't think it will work. The way forms are
processed involves special session-based security information to
prevent hackers from submitting a hacked form. Once you submit the
form (to get the preview screen) that session data is deleted and the
original form will not be
Ok, I'll look into this. You can force the desired behavior by
sticking in an extra space either after the link or in the line
between the link and the function. It's complicated all the reasons,
but I'll see if I can fix this.
Sorry I've been out of the loop the last week. Trying hard to get
caug
How about changing the code to this. Note the asterisks for the changed lines:
function BOLTinfoClean($info, $args) {
$before = count($info);
$exists = implode(',', BOLTsearchPageList(Array()));
foreach ($info as $p => $v) {
** $pp = BOLTutf2url($p);
**
On Thu, Apr 15, 2010 at 11:42 AM, Markus wrote:
>> > Proposal: Automatically move thefocusto the first text field. For
>> > example, before logging in you have to move thefocusto the text
>> > field to type your username. Same for search. Google does this too, by
>> > the way.
>>
>> Looked into th
It is a slight problem in the core distribution. If you go to
boltwire/barn/system and look at the site.auth.write page, you will
see a line like this:
login.admin:
This blocks people from creating the login.admin account. So if you
set your BOLTadmin to something beside admin (in index.php) it
On Sun, Apr 4, 2010 at 2:54 AM, Kevin wrote:
> I am surprised that there are many sites even considering allowing non-login
> editing of a site now days.
>
>
> On Sat, Apr 3, 2010 at 6:21 PM, Erlend Sogge Heggen
> wrote:
>>
>> Is this the way it's gonna be in future releases as well? Sounds to me
I tested a clean install--and it seemed to work fine... But looking
at the code action.create should not have the [] in the button (-->
name=submit[] ). Try deleting them and see if that doesn't fix it.
Also check to make sure you don't have a local action.create page. If
you do, update the marku
On Thu, Apr 1, 2010 at 12:47 PM, Markus Weimar
wrote:
> Many markups support specifying classes already. Any thoughts about
> links? I don't know where to put the class to not interfere with the
> link and the link name.
>
> [[a_page|class=red|A page]]
> [[a_page|A page|class=red]]
> [[class=red a
You probably just need to change the action list. Right now the edit
link only shows up when logged in--even if guests have write
permission.
Go to code.snippets and see if you can't rework the site actions
section so that the links you want do not require you to be logged in.
If you need more spe
Looks fine to me...
http://www.boltwire.com/index.php?p=test.indent
Cheers,
Dan
On Tue, Mar 30, 2010 at 8:59 PM, Kevin wrote:
> Markup
>
> ->
> This is a
> bunch of lines
> end
> <-
>
> ends up looking just like above instead of indented with the border on the
> left.
>
>
> On Sun, Mar 28, 201
On Tue, Mar 30, 2010 at 10:45 AM, Markus Weimar
wrote:
> On Tue, Mar 30, 2010 at 4:32 PM, The Editor wrote:
>> What would you recommend calling the parameter in the function?
>>
>> [(breadcrumb ?=?)]
>>
>> And/or should we just make it a config value?
>
>
What would you recommend calling the parameter in the function?
[(breadcrumb ?=?)]
And/or should we just make it a config value?
Cheers,
Dan
P.S. A silent list is a good list sometimes!!! Kevin, I still have
your emails in my to do box.
On Tue, Mar 30, 2010 at 9:12 AM, Markus wrote:
> Hello
On Mon, Mar 29, 2010 at 11:09 AM, Erlend Sogge Heggen wrote:
> Is there really no way around it? I'm all for security, but I just
> love seeing the cleanest possible URLs :) Would the security actually
> lessen if I use something like mod_rewrite to remove the .txt?
Erlend, just a quick note that
On Thu, Mar 25, 2010 at 5:00 PM, Markus Weimar
wrote:
> My list of issues is quickly shrinking. The last spacing/paragraph
> related problem I see is a missing paragraph around the first
> paragraph:
>
> [(list "{äpfel:tags}" fmt="[[{p}&tag={+p}|{+p}]]" join="
> ")]Even if I write here!
>
> [if
On Thu, Mar 25, 2010 at 3:52 PM, Markus Weimar
wrote:
> Why not make the backup action a real backup action. Click backup.
> Have a backup. Click restore. Have an exact copy. That would be a
> backup! :)
Actually this is one reason I'm leaning toward using the word package.
At some point someone
I am leaning toward doing this for 4.xx I'd be interested in hearing
any reasons to the contrary...
Cheers,
Dan
On Thu, Mar 25, 2010 at 5:56 PM, Markus Weimar
wrote:
> I would like that. It would make it easier to automatically open all
> BoltWire pages in a text editor. In OS X, I haven't fo
Great! I feel better about this solution, because I think I finally
understand what is happening. As far us the umlauts, I have no clue...
:)
Cheers,
Dan
On Thu, Mar 25, 2010 at 4:30 PM, Markus Weimar
wrote:
> Wow, this seems to be excellent. Thanks. I didn't add any line to my
> index.php and
Just a few comments on this thread...
First, I'm very encouraged by the input and the willingness of
everyone to pitch in. Great! I'm really happy to support this--esp the
part about not having developers not writing the docs! Cheers for
maintainers!
Second, Lino is right--one factor has been our
Assuming this last release turns out to be OK, we are ready to start
the transition to 4.xx. No major obstacles ahead...
My plan is to put out a stable 3.5, then run a 3.5 series trying to
get us as close to 4.xx as possible, and finish that off with 3.6.
Then for 4.xx, I will change ONLY the for
Wow, this is definitely getting to be a long series between stable
releases--but good news: there are NO vspace fixes in this release.
Suggesting we have flushed out most of the problems!!! If there are
no major issues with this release it will become 3.5.
There are some important fixes to the se
On Wed, Mar 24, 2010 at 1:16 PM, Markus Weimar
wrote:
> Didn't see your reply.
>
> Keeping site.language changes to a minimum is good, but till 4.x we
> should free ourselves and improve as much as we can.
Still, I would prefer to make the transition to 4.x as painless as
possible. A lot of forms
Just fixed this. Will be in the next release...
I also reindexed the entire site. Not sure why it was not properly
indexed. We probably need some way to regularly update and check pages
in the index to ensure it is always current. Not sure how to do that
best... Also remember, pages you don't hav
I don't want to go this direction Markus, because I want admin's to
have the flexibility to setup their installation any way they want to.
And this approach assumes a standard installation structure. Move your
farm somewhere unexpected and I don't think it will work as expected.
For example: my sit
Thinking through this a bit more, I agree you are right. BoltWire was
designed for variables like farmPath and imgPath to have paths, while
variables like farmURL and fieldURL to take URL's. Then when BoltWire
needs paths it uses paths. And when it needs URL's it takes URL's.
Given this, and the n
Did a small bit of research and testing and it seems either "disabled"
or "disabled=disabled" will work on the various form elements. It also
seems disabled='true' works, which I like the best... To allow
disabled=disabled or disabled=true in the markup we could simply add
"disabled" to the BOLTatt
Somehow there were some table rows without cells in them in the
source. Deleted these and the tables recovered themselves. I'm not so
concerned that BoltWire is a bit more particular about proper markup,
as long as it works properly when done right and produces good html.
There might be a way to ov
Some spammer I guess. I just deleted it (the title data field). Data
fields shouldn't be open to non-members. I need to check...
The more open we make the site, the more we will need good site
maintenance. I know at PmWiki.org (which is VERY open) there were
people constantly monitoring every chan
Can you explain what you mean by "disable"?
If we are missing some important form functionality, I'm happy to add it.
Cheers,
Dan
On Wed, Mar 24, 2010 at 9:44 AM, DrunkenMonk wrote:
> On Mar 24, 2:40 pm, DrunkenMonk wrote:
>> There doesnt seem to be a way to disable checkboxes in boltwire. I
On Tue, Mar 23, 2010 at 3:42 PM, Markus Weimar
wrote:
> 1) around table. Just to make sure, this is what you want:
>
> text
>
> [t]
> [r][c]cell
> [t]
>
> text
>
> ––>
>
> text
>
>
>
>
> cell
>
>
>
>
> text
This is what we want. If you put border=1 in the table you'll see
space between the t
Here's another release... Mostly small fixes and tweaks, and
additional work on the vspace issue. Those bug reports seems to be
winding down, so likely this version will become 3.5 stable fairly
soon, unless there are some things I've missed so far... Try the new
google interwiki. Kind of fun...
Just a note that the same fix I made to squelch the "Membership
Updated" message when logging in has to be made to the persist plugin
if you are using that. I just upgraded that, if you happen to be using
that plugin and getting annoyed with the messages...
Cheers,
Dan
--
You received this messa
On Tue, Mar 23, 2010 at 10:13 AM, Markus Weimar
>
> No! It's called favicon.ico! :D
Oh, I see. No idea what is causing it then... It shows up fine in
Chrome also... Haven't checked in Safari.
> The only thing in this thread still "open" besides the Safari issue:
>
> "Now, to prevent any clean
On page action I changed the wording at the top to this. It is more
accurate, as some actions may be blocked because of a lack of
permissions...
Below is a list of currently available actions:
As for the backup action, I changed the wording slightly to use backup
or backup file instea
On Tue, Mar 23, 2010 at 8:37 AM, Markus Weimar
wrote:
>
> As there is no complaint about the umlauts in the address when
> validating, I guess it's Safari's problem.
>
> This and the three previous posts are therefore obsolete.
I'm not sure I followed all of this, but will assume this thread is
c
On Tue, Mar 23, 2010 at 6:54 AM, Lino wrote:
>
>
> On Mar 23, 10:45 am, The Editor wrote:
>> The Tree plugin allows you to move files to new locations, but links
>> have to be fixed. I don't have any ideas for how to do that fixing
>> automatically, without s
Ok, wait until the next release. It probably will solve the issue.
I'll put it out as soon as I catch up on the emails... :)
Cheers,
Dan
On Tue, Mar 23, 2010 at 6:38 AM, Markus Weimar
wrote:
>
> Maybe your dev version fixes it? If I understand your suggestion, then
> no, this is not working:
On Tue, Mar 23, 2010 at 6:19 AM, Markus Weimar
wrote:
>
> Agreed with all agreements of you from above. :)
>
> What do you mean by "normal help files" and "generating" (from where?)?
>
> This is going to be an awesome help system!
Just that if we could generate those 6 pages of help files, I'd be
If you look at it carefully, when the condition is true you have a
line return after the closing div, but not before the opening div.
That's the imbalance that might be causing the problem. Though as I
said, it displayed fine for me. Did my suggestion work or not?
Cheers
Dan
--
You received this
On Tue, Mar 23, 2010 at 5:55 AM, Markus Weimar
wrote:
> No difference. Still the image has this address:
>
> http://localhost:/test/boltwire/farm/img/boltwire.gif
Is that not the right location?
> and still:
> img: ../boltwire/farm/img
> farm: http://localhost:/boltwire/farm
How do you
On Mon, Mar 22, 2010 at 12:14 PM, Markus Weimar
wrote:
>
> I think we can find a common denominator that brings advantages from both
> views.
Agreed. I like your proposal below...
> When I first saw the help system I was disappointed. I expected
> something like a formulary but what I found was
Can you go back and make one change at a time until you can figure out
what actually makes the mistake? My first guess would be to change the
ending to match the start:
[if][[#end_actions]]
Though I don't see any reason it shouldn't work as is... I just cut
and paste it into my test site and it
The Tree plugin allows you to move files to new locations, but links
have to be fixed. I don't have any ideas for how to do that fixing
automatically, without some kind of link indexing system... Perhaps
something could be generated as a plugin--though I'm not sure I want
that in the core. Not oppo
This should be improved in the next version of BoltWire. I basically
want to have the following show up differently in the browser:
text
[t]...[t]
text
and
text
[t]...[t]
text
Similarly, these should show up differently.
[t]...[t]
[t]...[t]
and
[t]...[t]
[t]...[t]
Similarly with blockqu
On Tue, Mar 23, 2010 at 5:15 AM, Markus Weimar
wrote:
> Maybe this could also lead to an easier way to link to other fields
> regardless of the server. I'm currently using this little hack:
>
> [if equal {port}
> 80][[http://{domain}/software_en|[^en.png^]]][else][[http://{domain}:{port}/software_
Markus, I spent a good bit of time digging into this and poring over
the php docs to figure out what was going on. Found a few things:
1) $$farm returns the value of $farmURL, not $farmPath, so setting
$farmPath in index.php will not change the value returned for $$farm.
I could not find any pla
This is a great idea Martin. I'd be happy to add an auto-increment
option. Info vars are easily extensible after all.
The easiest option would be a simple function like [(nextinfo
info.somepage)]. Reads the values and spits out the next available
number.
Then you could do
[(info field={(nextinfo
On Mon, Mar 22, 2010 at 10:36 AM, Markus Weimar
wrote:
> 1) In index.php before the engine call:
> $farmPath = 'http://' . $_SERVER['HTTP_HOST'] . '/boltwire/farm';
>
> Leads to:
> img: http://localhost:/boltwire/farm/img
> farm: http://localhost:/boltwire/farm
>
> Good.
>
> This works on
It would be a good idea to create that page, and allow people to start
adding content as they think of things...
Cheers,
Dan
On Mon, Mar 22, 2010 at 11:01 AM, Markus Weimar
wrote:
> Good decision.
>
> New user -> small site -> performance a non-issue
>
> Experienced user -> docs -> "Improving p
On Mon, Mar 22, 2010 at 10:22 AM, Markus Weimar
wrote:
>
> First, I would list the parameters for each function above its code.
> In my opinion a good function doc string tells you what the function
> does, what the parameters are, and what the function returns. At a
> minimum.
I'd like to see th
On Mon, Mar 22, 2010 at 6:56 AM, Kevin wrote:
> Did a search for header and ended up with a blank screen.
>
> the URL in the browser window says:
>
> http://www.tnet.com/main&action=search&myquery=header
>
> Which is not legal. There can only be 1 &. Subsequent passed options need
> to use ? or
Ok, I will make this change to the core. For both top and bottom
zones... However, the reason I switched them from the skin was
performance.
Anytime you can put something directly in the html, rather than a
zone, you save yourself thousands of processing calculations. Not
only do you have to read
Added it to the core. Thanks for testing this out for me. We'll see
if we get any problems with the change in other links not working. But
so far all seems ok.
Cheers,
Dan
On Sun, Mar 21, 2010 at 9:23 PM, Kevin wrote:
> This document was successfully checked as XHTML 1.0 Transitional!
>
> Appe
The problem was the nested tables (and other things). I will have to
work on that later, as it is important. But difficult...
Temporarily, I just uploaded a gif of the nested table. :)
I spent more time fixing all the other little mistakes and problems on
this page, to get it more current and acc
On Mon, Mar 22, 2010 at 9:34 AM, Markus Weimar
wrote:
> I am planning to contribute:
> - tabular API-like function docs
> - concise system pages with a structuring heading here and there
> - usability improvements to boltwire.com
> - making the docs homogeneous and concise and add more textual str
The default values, from engine.php, are:
BOLTdefault($farmPath, "$boltwire/farm");
BOLTdefault($imgPath, "$farmPath/img");
These can be preset to something else, but it must be done in
index.php before calling the engine, not after. Is this how you set
them?
$farmPath = 'other value';
Do you
On Sun, Mar 21, 2010 at 6:17 PM, Markus wrote:
> Argh, it's in the method docs. My brain is terrible at scanning
> CAPSLOCK. Are we going to create some API-like table for each function
> and its parameters? If we agreed on a common presentation for one
> function, the others could be created by m
$attr, $label, $missingPage);
> return BOLTescape('') .
> BOLTtranslate($label) . BOLTescape("$missingPage");
>
> Are these where you want the line added before?
>
> On Sun, Mar 21, 2010 at 5:03 PM, The Editor wrote:
>>
>> Try adding this just befo
Try adding this just before the last two lines of BOLTMlinks...
$link = str_replace('&', '&', $link);
~markups.php line 543. Let me know if that does it, and I'll add to the
core.
Cheers,
Dan
On Sun, Mar 21, 2010 at 5:26 PM, Kevin wrote:
> Almost validates now
>
> The only thing that it
On Sun, Mar 21, 2010 at 3:05 PM, Kevin wrote:
> Seems strange to add a blank line to remove the ... It worked
> though.
BoltWire basically explodes the output by \n\n and then checks each
piece to see if it matches certain criteria. If it does it gets
wrapped in . If not it is is ignored.
In y
On Sun, Mar 21, 2010 at 2:44 PM, Kevin wrote:
> Which means it is not using the default BOLTXlogin...
>
> It has in it:
>
> ..
> $BOLTid = $id;
> $BOLTmember = $member;
> $memberships = BOLTFmemberships(Array('output'=>'true'));
> ...
>
> Instead of:
>
> ...
> $BOLTid = $id;
> $BOLTmember = $mem
one that the messages is in and found that instead of what
> should be there:
>
> [messages]
>
> The [messages] had be physically changed to:
>
> Form submitted. Preview Mode.
>
> Editing that by hand in Unix, the site doesn't seem to have any issues.
>
> I
Mine do not show up... Can you confirm this again after I get out 3.4.10?
Also, do you have a custom login form? Perhaps with messages set in
it? If so, try changing line ~307 in commands.php to this:
$memberships =
BOLTFmemberships(Array('msg_func_memberships'=>'false'));
Perha
Sorry Markus, I steer a way from cleanURL questions. :(
I did find on my site(s), however, that setting a $farmPath to the
full url, rather than a relative url solved many problems. I think
perhaps the relative path is adjusted to work off the aliased url of
the page rather than the original link
On Sat, Mar 20, 2010 at 2:54 PM, Markus wrote:
> First round to reduce clutter and wordiness on system pages. (And
> remove workarounds for line spacing issues that are no longer needed.)
>
> I improved action.backup quite a bit (I hope you agree). Just have a
> look at the code and test the added
Try changing the snippets to this
> [[#actions]] // line break here...
> * [[main|home]] [if ! login]
> * [[{p}&action=login|login]]
> * [[action.register|register]] [else]
> * [[?{p}&action=view|view]]
> * [[action.create|create]] [if][if auth write check={p} && login]
> * [[{p}&action=edit|ed
I've fixed the preview issue for the next release in the core. NO IDEA what
was causing this on your site. It's not doing it on mine in 3.4.10
(upcoming). If it still does for you, I'll explore more, but my guess all is
ok now.
If it isn't fixed with 3.4.10, perhaps you could send me the form that
501 - 600 of 2388 matches
Mail list logo
