contentPane or ContentPane discrepancy

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

Please do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.

This forum is for discussing mojoPortal development

This forum is only for questions or discussions about working with the mojoPortal source code in Visual Studio, obtaining the source code from the repository, developing custom features, etc. If your question is not along these lines this is not the right forum. Please try to post your question in the appropriate forum.

You can monitor commits to the repository from this page. We also recommend developers to subscribe to email notifications in the developer forum as occasionally important things are announced.

Before posting questions here you might want to review the developer documentation.

Do not post questions about design, CSS, or skinning here. Use the Help With Skins Forum for those questions.
This thread is closed to new posts. You must sign in to post in the forums.
9/12/2005 3:11:16 PM
Gravatar
Total Posts 45

contentPane or ContentPane discrepancy

While scanning some of the SQL code I noticed that sometimes "ContentPane" was spelled "contentPane".  Not sure if this has caused any problems yet.

Search in 4CreateData.sql in all three supported database scripts.  This is where I first noticed the discrepancy and started looking at the code.  I used find to search the whole solution in Visual Studio to reveal more discrepancies.

I am using mojoPortal from svn r498 9/11/2005.

9/12/2005 4:11:27 PM
Gravatar
Total Posts 18444

Re: contentPane or ContentPane discrepancy

It would be nice if it were consistent but I don't think its causing any problems, its just an id for a td in the markup and that should be case insensitive on all platforms. Nevertheless, I may look for it and fix it sometime soon.

Joe
You must sign in to post in the forums. This thread is closed to new posts.