Posts in Category: Development

SVN Heads Up from Novell Forge

Just thought I'd pass along a heads up from Paul at Novell to Novell Forge svn users. Accessing the mojoPortal svn repository might be a little bumpy on monday during the transition, but https access will be a little more firewall friendly so this transition will be a good thing. After the transition I'll update the instructions for svn access to mojoPortal

Hello again,

Monday, 13 Mar 2006 we will be migrating all subversion projects to the new server.  This will cause intermittent outages during that afternoon MST.  The new server will continue to allow ssh access for users with commit access, but will no longer support anonymous ssh access.  There will also be https access for both anonymous users and user with commit rights.  If you desire, you will also be able to mount your repositories as a davs drive.

The website will be updated with the new information at the same time.

If you are using ssh keys to allow scripts you access your repository you will need to accept the new server fingerprint.   All of your public keys will be moved to the new server.

Please let me know if you see any problems and I will respond as quickly as I can.

Thank you,

This Page Is Valid XHTML 1.1!

I did a little more tweaking and now This Page Is Valid XHTML 1.1!

Again you have to try it with the source from a browser like Firefox, if you just point the validator at this page it renders down level which is not compliant.

I should note that the FCKeditor is only XHTML 1.0 compliant so any page with an editor will not validate against XHTML 1.1 until that support is in place. In any case since browsers seem to be forgiving I think I can still go forward with the XHTML 1.1 DOCTYPE

Also I had to fix even more content in the db where I have historically had the bad habit of using target=_blank on links to external sites. target is no longer valid in XHTML 1.1

This site is also currently using much more CSS layout and most of the table layout has been removed. I'm still working on a few areas of this and still need to update more of the built in skins to work with the new model but I figured it was good to go ahead and do the skin for this site first so I can test it in the real world.

Thanks go out to Alexander Orlov for help and good advice in working toward XHTML compliance.

This Page Is Valid XHTML 1.0 Transitional!

After a good bit of work, according to the Wc3 validator page, this page is Valid XHTML 1.0 Transitional!

Now if you want to confirm this yourself I will say you can't just enter the url and have it come up valid becuase when the validator pages makes a request it is rendered differently than when using a browser. In other words the .NET Server controls do their down level rendering when it can't detect the browser and apparently the downlevel rendering is not valid.

If you view this page with Firefox and then right click and view the page source then save this file as www.mojoportal.htm and upload it to the validator it gives it the nice approval.

Ultimately I would like to get to Strict compliance instead of Transitional but this is a step in the right direction.

Another factor that comes into play in a CMS like mojoPortal is whether the existing markup in the database that has been entered using the CMS features conforms. I think in general FCKeditor does produce valid markup, but I have found places where I edited stuff directly as source and I didn't do it with XHTML validation in mind at the time so I am cleaning things up in the content as well as in mojoportal code. For example using a valign attribute on a td is not valid for Transitional and moving forward toward Strict, links with a target attribute are not allowed so I am cleaning up things like that too.

I doubt if all the pages in this site are currently valid but I am making progress and eventually we will be able to proudly display the icon

2.1 branch svn heads up

I just committed some major changes in svn on the 2.1 branch. You may want to hold off for a couple of days on getting latest. It will build but if you use any skin other than theblues1 it will be broken at run time.

I've been going through all the modules and pages and changing to CSS layout and now I need to go back through the other skins to fix them like I did with theblues1 skin. I should have things in better shape over the next few nights. I was going to wait until it was all working before checking it in but then again I hate to keep this much work checked out and another developer who is doing similar work in the 1.x branch needs to see my work.

Update 2/13/2006: I just commited at least enough fixes that you don't get runtime errors with any of the built in skins. Still the only usable one is theblues1 as the others all need some css work to fix the layout and style. I'll be working on those. If you have your own custom skin, you will need to get the 3 new Panels named divLeft, divCenter, and divRight and add them to your skin and then you will probably have to fix some style to get the layout right. There are some new classes for css, right now theblues1 css has all the right classes, you will need to get the missing ones and add them to your css and probably tweak them to fit your needs.