3.3: final preparation and performance

BUG LIST
(as of 8:30 PM PST time):

• The default template’s style.css is blank (0kb).
• The installer doesn’t create the TV’s neccessary for the menu and the RTE blogpost from the NewsLetter snippet.
• Ryan’s email address (and possibly password) are used in the siteadmin webuser account.
• FCK Editor size is way to small within manager now.
• Admin’s (manager user) email still reads "Your email goes here" instead of an actual email address (needed for the NewsFeed snippet.

Many thanks mark. Will have a look at these

Thanks Ryan !

regards,

Thanks Ryan? I had nothting to do with it! lol

Quote from: rthrash at Oct 19, 2005, 09:09 AM

Thanks Ryan? I had nothting to do with it! lol

Its related to this post http://modxcms.com/forums/index.php/topic,1107.msg7213.html#msg7213
;)

lol... wrong thread.

I nailed down the issues with the IE errors, now it’s time to focus on the styling tweaks. The problem actually was due to a missing sleight.js file which provides support for transparent PNG files in non-background images for IE. The behavior and scriptaculous stuff had nothing to do with it!

I’ve also now cleaned up much of the stylesheets so that it renders mostly the same in IE... in fact, got rid of the IE-only stylesheet entirely (less to download). See the results at Pixelhick.com. (still need to finalize the contact form though)

Two small but fix-worthy remaining issues for the default full site install content:

1) Can we programatically get the email address of the Manager user ID 0. I would like to use it as the default for the contact form.

2) Can someone help me get to the bottom of the backslash issue found in the blog section. Look at the topmost Safari entry for an example. When displayed as a standalone article it has no backslashes. When displayed as a summary, it does.

Why not use [(emailsender)]?

Quote from: rthrash at Oct 19, 2005, 01:33 PM

2) Can someone help me get to the bottom of the backslash issue found in the blog section. Look at the topmost Safari entry for an example. When displayed as a standalone article it has no backslashes. When displayed as a summary, it does.

Why not add a preg_replace to replace any /’ with ’ ? That would solve the issue nicely, although it wouldn’t explain where they come from in the first place.

Could the problem be that the parser does a stripslashes on ’content’ but not on ’intro_text’ or whatever it’s called in the database?

In the function mergeDocumentContent, there is a stripslashes, but in all the other merge... functions there isn’t. I’m not sure which one of those would handle the intro_text string; mergeSettingsContent or mergePlaceholderContent, but none of these do a stripslashes.