Unfortunately, only putting <br> tags at two line breaks or more wouldn't
work because sometimes you might have a list on a page like this:
item1
item2
item3
That would come out all jumbled up without the line breaks. And actually,
this is the very thing that was broken before. Multiple line returns worked
fine. It was just some of the details before and after divs, includes,
tables, blockquotes when there was one or two linebreaks before or after.
Now it all works perfectly, before it was hit or miss.
Can you give me an example of the problem with css and counting elements?
Maybe there is another workaround...
As for the test page and data action bug, I'm not seeing them. Can you send
me a link somewhere so I can see what you are describing?
Can you tell me which specific vars you are having trouble with? The path
variables should give a relative path and the url variables should give a
full url. That's so you can use them to reliably get graphics from wherever
they happen to be. I used to have a different setup, but this works far
more reliably...
The "$rs" part just provides http or https based on your context (request
scheme). In 7.xx I forced https--but then had problems with my localhost
setup. So this simply fixed that (for me). But reading your note again,
maybe your setup isn't getting the value for that variable... You can see
that rs is defined at the top of variables.php. If using request scheme is
not reliable (sounds like it) I could try something like this instead:
if (! isset($boltURL)) {
if (strpos($SERVER[HTTP_HOST], 'localhost') !== false) $boltURL =
"https://$_SERVER[HTTP_HOST]/";
. 'boltwire';
else $boltURL = "https://$_SERVER[HTTP_HOST]/"; . 'boltwire';
}
Let me know if that works. I'll be happy to put that in the next release...
As for the gui, did you update the code form as I suggested? As you can see
on the BoltWire site, the gui buttons work just fine. But I did have to
update the paths in the core page. If you have an older local version it
would definitely break. But obviously if $rs is not being supplied that
would break it even more! :)
Cheers,
Dan
On Wed, Aug 26, 2020 at 3:43 AM mz <[email protected]> wrote:
> Thank you for your quick and comprehensive answer.
> A solution to spacing could be to insert a <br> only after two consecutive
> carriage returns like before.
> This avoids problems with css that is based on counting elements and that
> works in code.embed as well as in text editors but not in BoltWire page
> editing.
>
> More observations:
> Creating a new page "test" returns the "welcome.newsite" page (in 7.07
> too).
> action.data starts with the word "test"
>
> For me the shared and system variables start with "://".
> This scrambles the gui image path as well as the new members page path
> mentioned above.
> I see you changed the bolturl path in variables.php to "$rs://...".
>
> I did not touch anything except of adding a htaccess in the folder my url
> points to and that contains the BoltWire folder and my field folders.
>
> htaccess isn't new:
> RewriteCond %{HTTP_HOST} ^(.*)example\.com(/|$) [NC]
> RewriteRule ^(.*) /field/index.php?p=$1 [QSA,L]
> returns example.com/folder/page
>
> Setting index.php in my field folder skips the folder in the url isn't new
> either:
> $cleanURL='http://www.example.com/';
> $fieldURL='http://www.example.com/field'; (--> no slash at the end
> because of files and skin paths)
> returns example.com/page
>
> Since I am asking:
> I use a form to populate and edit info vars (command info).
> Is it possible out of the box that an empty form text field deletes the
> values of an existing info var (except of using minus)?
>
> Greetings, Martin
>
>
> Dan schrieb am Dienstag, 25. August 2020 um 17:13:08 UTC+2:
>
>> Thanks for spotting the extra library.php! I'll delete and re-release...
>>
>> Where did you see the broken links? I'm not seeing that on my site. Is
>> this a vanilla install, or an established site? I'm wondering if some
>> variable path was changed...
>>
>> Is it an existing edit box with gui enabled? If so, you might try
>> inspecting code.embed.gui and make sure it uses paths like this:
>>
>> <a href="javascript:insMarkup('**','**','Bold','{+guiid}')"><img
>> src='{+system}/files/gui/bold.gif' title='Bold' style='border:0px;' /></a>
>>
>>
>> Or you could just delete your local version of that page and use the core
>> one--unless you have customized it.
>>
>> As for the <br> issue, the new system will definitely change some page
>> displays. In the above example, it seems the new output is now actually
>> more intuitive. That is, when there is a linebreak in the page content,
>> there is a linebreak in the output. And when there is not, there isn't. I
>> think that is what I was aiming for.
>>
>> Actually, that's why I went this direction--because in pretty much every
>> place I found a need to fix up my vertical spacing, the output didn't match
>> the input. Usually, there ended up being some workaround I just had to undo
>> to get my display to correct itself. Going forward, it seems like it is
>> going to be much more rock solid intuitive. What you put in is what you get
>> out.
>>
>> One option I could add is using the ` escape character at the end of a
>> line to escape the <br>. I've also thought about (but haven't done yet)
>> using a leading '.' to indicate that line should be wrapped in a <p> tag.
>> But I have not yet really seen a need personally for either of these...
>>
>> Anyway, let me know where you saw the bug and maybe the underlying page
>> content, and I'll see if I can track it down and re-release this.
>>
>> Cheers,
>> Dan
>>
>>
>>
>> On Tue, Aug 25, 2020 at 9:42 AM mz <[email protected]> wrote:
>>
>>> Thank you very much for this update. Very appreciated.
>>>
>>> Some observations:
>>> I found a library.php in the shared folder, I suppose that was copied
>>> somehow there.
>>> The urls of the gifs of the editor are wrong:
>>>
>>> http://www.example.com/field/://http://www.example.com/boltwire/system/files/gui/ul.gif
>>>
>>> A not so nice outcome of the new spacing system is that when you put in
>>> a line-break you always get a <br>.
>>> That means you can't do as before:
>>> <div> something </div>
>>> <div> some other thing</div>
>>>
>>> but you have to do: <div> something </div> <div> some other thing</div>
>>> Depends on the css, I suppose.
>>>
>>> Greetings, Martin
>>>
>>> --
>>> 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 [email protected].
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/boltwire/f8ddc369-bb69-4ad3-bbc5-fdf4db400479n%40googlegroups.com
>>> <https://groups.google.com/d/msgid/boltwire/f8ddc369-bb69-4ad3-bbc5-fdf4db400479n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/boltwire/0a12f306-c096-4b91-8308-e56f2c991fbbn%40googlegroups.com
> <https://groups.google.com/d/msgid/boltwire/0a12f306-c096-4b91-8308-e56f2c991fbbn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/boltwire/CABnVu_55N5we1nTNJqtrqzO00smY5LonmEe-a_w1o38Qg3YYEw%40mail.gmail.com.
