Does version 1.0 have the ability to create more or less static content pages for items like Terms of Service, Privacy, etc.?

I think this was functionality provided by the apage mode once upon a time. It's been a few years since I last looked at WebApp, but we're getting ready to port our entire company infrastructure from PHP to PERL and WebAPP fits one of our needs perfectly aside from the need to create some semi static pages.

I think we can make Articles work if need be, but I was just wondering if pages made it into the Version 1.0 release.

I've tried on 3 seperate accounts. Two are dedicated servers, one is a shared hosting account and failed on all three.

Account 1 is a shared debian host we use for non-critical and anything we deem to be a security risk: i.e. anything not coded by us. That includes any CMS systems like webapp, joomla, wordpress etc..

Account 2: is a CentOS dedicated server we have root access to and use for development and is managed using plesk. Here I got a forbidden error even though everything is CHmodded corrected and ownership is the same as the other files and directories and we can access them.

Account 3: Is one of our production machines, a managed Dedicated server with FreeBSD. I've read the post about FreeBSD, but Pair Networks is pretty Perl friendly. (They already have just about every Perl module worth having installed by default)

All machines are running Perl 5.8.8, save for the CentOS server, which is running 5.10.

That being said, I've been busy working on other projects. This hasn't been the highest of priorities until now. It's been 5 years since I've touched PERL for CGI. So time to relearn all the tricks I've forgotten.

Apparently Cyberduck isn't all that smart, although it may have been BBedit as well. Either way I switched the encoding to Western (ASCII) and Unix LF in BBEDIT, saved and no more CGI errors on the BSD server. Now to try again on the Linux servers and see if that is the problem.

For the life of me, I can't figure out where in Cyberduck I can force ASCII. I may need to boot into XP and see if that ancient copy of WS_FTP_95 still works.

unimatrix said 10 minutes and 44 seconds ago.:Okay, I can now get to step 2 of the install. But it gets to site theme and the page appears to stop, nothing is pulled into the select box and there is no button to continue:

Ouch.. an install button, luckily no one but you has the cookie to proceed there, so nothing to worry.

Otherwise it is peculiar, all I can think of is that maybe because the repeated install attempts that something got messed on the way, incomplete extraction of files may be one of the causes.

A simple solution would be to rename the folder where the install took place and retry a fresh install, but before doing that it would be a good idea to take a look at the install log. You can find it in the install folder.

I'm not sure if this has been covered before. But I ran into this very same error and got around it by using a script that converts line ends to unix. I think the name of the script was "dos2unix" and I found it on the web.

Once I got the line ends of ALL files in the zip archive converted, everything worked perfectly.

Aimod said 19 minutes and 36 seconds ago.:Hi there. Im sorry but Swetheme is not updated to current version. Maby if i get the time ill do it tho. Been awhile since i made that one :) nice to see it requested.