The Mojoportal Installer in the Windows Web App Gallery is out of date. Would you update this to version 2.3.5.5?

Joe, there seems to be a problem installing 2.3.5.5, either with the web apps gallery at my host, or even with the web platform installer -- the wpi error says "downloaded file failed signature verification and may have been tampered with."

I also tried once again to a manual install, and still cannot do that -- it just keeps telling me it can't contact the database, no matter how I try to finagle the connection string.

So, I'm here wanting to set up a new mojoportal site, and cannot get the thing installed.  At this point I may just copy my installation of 2.3.5.4 from my new blog site, change the db/user/pw strings in user.config, and see if I can get it to fly that way, because I cannot get 2.3.5.5 installed by any means.

Andria

I successfully installed v2.3.5.5 using the Web Deployment Tool in IIS Manager (on Windows 7 x64). Because I had the default version of 2.3.5.4 installed I first used SQL Server Management Studio to delete the mojoportal database and users. Then I deleted the inetpub\wwroot\mojoportal directory. Finally, I used the Web Deployment Tool to install mojoportal.

Thanks for that tip, Jamie; apparently my host does use IIS7, but what is that "pipeline" bit?  And how would I know if they're using it?  Should I just go ahead and specify my site's URL in AppKeepAliveUrl anyway?  I looked all over the dotnetpanel at Mocha, but there is no reference to the application pool, or anything having to the do with the server itself.  Yeah, I know, you get what you pay for; someday maybe I can afford "managed hosting" where the host admin will actually do what I want them to do -- but I need those 6 lucky numbers first.

Joe, that's a real bummer, since my Linux host is on such a MUCH faster server, but I'm not surprised; adding a layer of complexity to any of this seems to add an order of magnitude more problems.  I'll just keep hoping I can at some point afford a faster host.  Although if I can fix this "keep alive" problem, maybe this one isn't so bad -- just no tech support who's prepared to do anything except give me links to their knowledgebase -- god forbid they should ever READ what I write them and then WRITE back an appropriate answer.  Maybe they're outsourced and just don't speak English!

Thx!!

Andria

Yep, it really does, it makes a huge difference.  It's kinda odd; I had noticed this slow-start thing with subsequent Mojo sites I setup -- subsequent to the first one, when I knew absolutely NADA! about asp.net or mojo or anything else about a windows server, but I had seen that "keep-alive" thing in web.config when I was first perusing it, trying to get a feel for how this whole shebang works -- and not knowing what I was doing, I set it to "true," though I knew nothing about the pipeline/url business, so that line was still blank -- but that site remained faster than any of my other mojo sites, though until now, I had no idea why!!!

Yeah, I really could use a slap in the head sometimes.  

So anyhow, going by that performance in my first site (the link is shown over there in the left column under my pic) it might be that I don't really need to have the URL setting, just the "true" part.  I have no understanding at all of windows servers, so I really have no way of determining about the pipeline thing, unless I just ask them (the host "tech support" -- that's what they call it; I call it a whole durn call-center of full-fledged morons), and I'd give it maybe 50/50 as to whether:  a) I get an answer at all that's pertinent to the question, and/or b) the answer would actually be correct.  *sigh*

But anyway I fixed that slow-start thing for all my mojo sites, so I am a happy camper.  I got another of my largely-inactive-because-it-was-such-a-damn-hassle-to-update Joomla sites moved to Mojo and didn't even have any problems with DNS or my host's weird error msgs to get it done, so again, happy camper.

Mojo just rocks, that's all there is to it.

Andria