On Sep 29, 12:14 am, Markus <[email protected]> wrote:
> Image styles like hspace='25px' are inserted twice when I use them
> directly on the page (not in the css file).
>
> Thepopupextensions is broken (others too?). Try 
> validatehttp://www.markusweimar.de/software/otrdecoderx. Thepopupcode is:
>
> [(popuplink="http://www.abc.x.png"; label=[^x.png^] height=348
> width=758 resizable=false)]
>
> Also when I put styles on the page I get "duplicate specification of
> attribute "style"" and "XML Parsing Error: Attribute style redefined"
> when validating. Try validatehttp://www.markusweimar.de/software/uebersicht.
> The code is:
>
> [[page|[^picture.png style="vertical-align:middle;margin-right:
> 1em;"^]]]

Scratch that. Absolutely no idea why this happened after upgrading but
it's gone. Sorry for any confusion.

> On Sep 28, 11:28 pm, The Editor <[email protected]> wrote:
>
>
>
> > Can you give me a link to look at? Or is this only offline testing?
> > Can you check the html output and see if you spot what the problem is.
> > I did rework the code for local field and global farm images. Which is
> > it in this case? Any help you can give me to debug is appreciated.  No
> > clue about the page loading process. Seems it should be a skin
> > issue...
>
> > Cheers,
> > Dan
>
> > On Mon, Sep 28, 2009 at 5:19 PM, Markus <[email protected]> 
> > wrote:
>
> > > Hi,
>
> > > I have an image in 'top' which is not displayed any longer on some
> > > pages. I am not sure what these pages have in common. German Umlaute
> > > in their title? (I mean title, not page name. I have no page names
> > > with Umlaute.)
>
> > > Then there is this strange page loading order. This is also the case
> > > for 3.15. Some pages will load the background of main first and then
> > > display the text on it. This is good because when you switch pages
> > > your background does not flicker once. Then there are pages where the
> > > main background is first rendered with the background color of your
> > > wrapper and then with the background color of your main but only
> > > _after_ the main text is rendered. This is bad...
>
> > > Regards, Markus
>
> > > On Sep 28, 10:48 pm, The Editor <[email protected]> wrote:
> > >> I've just zipped up and released the next version of BoltWire: 3.16.
> > >> This one has many bug fixes, and some rewiring of the core code.
> > >> Including what I hope/think is a fix to the bug causing my server
> > >> errors earlier last week. There are also a few new enhancements,
> > >> particularly under the hood kind of stuff. There is nothing here I see
> > >> as especially problematic--in fact we may have some future bugs clear
> > >> up by themselves--but with this many changes surely something is
> > >> likely to impact something else, somewhere. I'm waiting a day or two
> > >> before uploading my site just to see if you all report anything!  :)
>
> > >> Anyway, here is the list:
>
> > >> * Slight fix to the code generating farm img links, resulting in some
> > >> malformed urls, which possibly caused the major server problems
> > >> encountered earlier this week (evidently a glitch with the php
> > >> getimagesize function).
> > >> * Added a BOLTingroup function to engine.php and rewrote the admin,
> > >> editor, and ingroup conditionals to take advantage of it (all three
> > >> also now take an optional id= parameter). Should greatly ease
> > >> development of plugins.
> > >> * Under the hood change, splitting part of BOLTMfunc off into
> > >> BOLTfunc, and updating comm2func to take advantage of this. Should not
> > >> produce any noticeable disruptions, but gives developers a better
> > >> access point to the function engine. And clear connections between
> > >> commands and functions.
> > >> * Slight fix in the BOLTargs function to properly handle the myBOLTargs 
> > >> hook.
> > >> * Did some strip slashing of the if functions in an effort to track
> > >> down some bugs.
> > >> * Made it possible to set count=false in a search box to avoid the
> > >> search limit feature, and updated site.index to use it.
> > >> * Added a line to BOLTargs to help escape parameters containing 
> > >> contractions.
> > >> * Added a hook to BOLTexists for (potential) use in creating alternate
> > >> page store mechanisms.
> > >> * Reworked skin selection routine when dealing with the RSS hiearchy
> > >> to avoid errors.
> > >> * Marked action.register for the translation engine
> > >> * Allow {id} in site.auth pages, to customize permissions further.
> > >> * Fix bugs in loadpage function to improve matching of anchored sections
> > >> * Rewrote the new mail function (again) to give better control over
> > >> body output, with content=simple, html, and custom rules. If nothing,
> > >> all output is escaped.
> > >> * Re-added the "mailmode: active" site config option to change the
> > >> default from demo to active when mode is not set in the function/form.
> > >> * Some reworking of the markup table to put a few rules in different
> > >> groups, to simplify output.
> > >> * BOLTsavepage now resets, rather than clears the $BOLTpageStore after
> > >> a page is edited, which might save a file read or two.
> > >> * Fix preview function to show proper line spacing of form and session
> > >> elements in preview mode.
>
> > >> Two bug reports I could not track down (replicate) and therefore did not 
> > >> fix:
> > >> * Fix translation of commands.php line 158-159
> > >> * Problem "`{:title}" working, but not "`{title}" in a mail form.
>
> > >> Please give the new release a good run. I think it is a big release. I
> > >> still want to do a little more digging into the url2utf conversion
> > >> process and try to simplify it, but that will have to wait till
> > >> another day. I just wanted to get out what I have. At least most of my
> > >> todo list is cleared out at last.  Enjoy!
>
> > >> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to