Upgrade reporting mojoportal-core schema up to date when it

Upgrade reporting mojoportal-core schema up to date when it isn't

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

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/11/2010 12:24:04 AM

epte

Total Posts 10

View Posts

Upgrade reporting mojoportal-core schema up to date when it isn't

I installed 2.3.4.4-net35-pgsql just today. I piddled around with it a little, adding some pages, adding a fake forum and post. I updated my mercurial clone up to 35779f73ecb5 which Joe posted on 2010-09-08 11:02:46 -0400. I built and deployed and went to the Setup/Default.aspx page and got this:

Probing system...
File system permissions ok.
pgsql database connection ok.
database permissions are sufficient to alter schema.
database initial schema already exists.
database core schema is up to date.

...

Database Platformpgsql

Version2.3.4.4

StatusYour installation is up to date.

But I can see this in Setup/applications/mojoportal-core/SchemaUpgradeScripts/pgsql

(snip earlier files)

2.3.4.3.config
2.3.4.4.config
2.3.4.5.config
2.3.4.6.config
2.3.4.7.config
2.3.4.8.config
2.3.4.9.config
2.3.5.0.config
2.3.5.1.config
2.3.5.2.config

And I confirmed that all dll's have the timestamp of my build, and not of my 2.3.4.4 install.

Weird. I've run out of ideas where to look. Thoughts?

Thanks,

Erich

9/12/2010 7:05:34 AM

Joe Audette

Total Posts 18439

View Posts

Re: Upgrade reporting mojoportal-core schema up to date when it isn't

I would check the error log for any clues, maybe file permissions are not right. /Data/currentlog.config is the log file.

If it doesn't run the scripts it usually means they are missing but it could also mean it can't read the files.

But really if it says your system is up to date it sounds like it is not really running the latest code as you think it is. Maybe you had deployment errors and it did not upload the newest dlls in the /bin folder

9/13/2010 11:09:24 AM

epte

Total Posts 10

View Posts

Re: Upgrade reporting mojoportal-core schema up to date when it isn't

Thanks Joe, for the hints.

It turns out the stuff in /bin didn't deploy for whatever reason. I reran my deploy scripts (which I swear I did before), and it worked this time. Strange.

I'm set for now. :-)

Erich

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