|
|
 |
 |
|
 |
|
| Demo Main Page: |
Main Page |
| Demo Admin Page: |
Admin Page |
| Admin Username: |
admin |
| Admin Password: |
demo123 |
|
This demo will be deleted and reinstalled in
|
|
|
 |
|
 |
|
|
|
|
|
 |
upgrading from 0.10.x to 1.x is actually pretty simple. there is a convert page, www.yourdomain.com/convert that will upgrade your content. Announcements, menus, webpages, article manager etc. I converted 150+ branch sites and lost NO content. images and docs have to be moved manually, but overall it was painless. I recommend using a new database and keeping the old one intact, it will even convert your users.
I am loving 1.6.3, and the community is growing as is the support from App State on the unofficial forum site.
|
|
phpWebSite is my first CMS too way back 2004. this year onwards, 2009, I was thinking of using the same CMS as well as I am interested to avail of the module particularly the members profile. to some extent, the newer version 1.6.3 has user preference disturbance unlike the old version 0.10.x - I having a thought now of using another CMS instead of phpWebSite. Any good CMS suggestion from any of you as my project is based on Members Profile's JobHunt for Employers future references and the like?
|
|
Beware, the phpWebsite project gives NO UPGRADE PATH when they release major versions. They gave no way to upgrade from 0.9.x to 0.10.x when that came out, nor from 0.10.x to 1.x when that came out. So basically you have to install new and manually migrate data over, which is error prone and can take hundreds of man-hours to do. This is the reason I'm looking for a new CMS now, I won't stay with these guys if they won't support full version upgrades.
|
Hmm.. I started with the earlier versions of phpws (0.10.x series) and what I really liked was the dead simple end-user (content-editor) interface. Secondly, the code is object oriented making it easy to understand and extend.
What I didn't like was that layout and style directives were dispersed throughout the code. Although the system uses themes, each time you created a custom site you still had to trawl through modules to catch odd places that styles were defined.
Please note - a long time ago the project moved on to version 1.x. At that time there were severe layout issues on my particular browser/os platform. I raised them as issues but because I was not operating on a LAMP system was pretty much told my issues won't be addressed.
From what little I'd seen of the 1.x series I preferred the 0.10.x versions and wished someone would just run with that branch and fix up all the little issues that people kept raising.
Based on the above, here are the changes I would have liked to have seen in the 0.10.x series in order to have a pretty robust, beginner-friendly CMS:
Use only the wiki module, and not the pagemaster or article modules. Wiki retains all versions of edits, making it foolproof for beginning content editors.
Add per-page permission to the wiki module as per the hack that was there for pagemaster (using user groups).
Add a new field to each wiki page for "summary" and route this to the homepage as a list of announcements, replacing the Announcements module (subject to checking a flag).
You now would have a robust engine for creating web pages, very easy and fast linking between pages (even those that don't yet exist), the ability to style your content rather easily, group publishing permissions and a homepage "what's new" stream (oh yeah, and add rss to that feed too).
Use uplink instead of Documents. Add stats to the number of times uplinks get downloaded and add syntax to the wiki to define the target for links. Finally, write a front-end javascript WYSIWYG editor for the wiki and create a menu manager that outputs a standard unordered list for its menu so you can use javascript to animate it.
Right now, it seems that the biggest requirement for many small-scale websites is ease-of-use by content editors. I'm looking at compactcms right now and there are a few others that fit this bill. Sadly, I ended up finding that phpwebsite would take *ages* to customise satisfactorily, and for small-scale clients it just doesn't pay to do that. A shame given I've coded about 10 sites with phpws.
Final note - bear in mind I'm talking about the older release.
|
|
Hi All, phpWebSite knowledge is spread amongst many sites. Still, when you try to limit your search to 'phpWebSite', you get many sites actually running phpWebSite -- not the ones having phpWebSite knowledge.
I'm working on a phpWebSite directory to make life easier for hunters of wisdom. It already has a dedicated phpWebSite knowledge search, based on Google Co-Op. You can find it at
[phpws.info]
Enjoy!
|
|
Hi Tips, phpWebSite 1.0 supports clean URLs. Look for example at the official homepage http://phpwebsite.appstate.edu/. Also, for prior versions, there is a thing called the 'superhack'.
|
|
I installed PHPwebsite, and then tried to find a way to configure clean URLs. I couldn't find a way to do it. The URLs are not search engine friendly, and even the links back to the home page sometimes have strange URLs like '/index.php?&MMN_position=1:1'. Unless they can find a way to make search engine friendly URLs, I can't use it.
|
|
I find PHPWebsite easy to use, but not as intuitive as E107, which is what we are now using, however more intuitive than Mambo. PHPWebsite is slow, very, very slow compared to other CMS that we've tried. Their website has all the information you need for help, once you figure out how to navigate around it.
|
|
Installed, uninstalled and installed and on my way to uninstall it again. It looks promising but there is still an issue with creating menu on Windos XP, running the latest version of LAMP.
The learning curve is not tedious but getting around could make one become dizzy.
|
|
I used phpWebsite for a little over a year. It was my first CMS. It was fairly easy to install.
My biggest complaint was that phpWebSite was a fairly large install (10k files) and became difficult to maintain once I had customized it. This is a tradeoff though. I chose not to use the built-in forums or photo gallery. I preferred the coppermine and phpBB packages for photo gallery and forums.
|
|
Hello all, referring to the post of Oreb Nightchough. I have a compiled a list of all existing free themes for phpWebSite, there are quite a few out there. You can find this list at http://themes.kiesler.at/
Actually, getting a phpWebSite validate is not too hard. You need to get the templates and themes right, that should do the trick. I'd gladly help you through it, please visit the forums on my home page if you want to to discuss further details. Best regards, Ren C. Kiesler!
|
|
I have used phpwebsite for the past four years for our Community Centre's Website. It was easy to setup and I found the theme templates easy to manipulate and customize. Older versions did have problems with block movement and other quirks but the latest version is very stable and has few problems. All the problems I have come up against in the past were fairly easily solved even the creation custom modules. I hired senior year programming students to customize phpwebsite to integrate with our point-of-sale system they found the php-code simple to understand. As with all CMS's out there this one may not have what you are looking for, but if the features you want are there, then phpwebsite should be a breeze to use. The major plus for us is the slow and steady development curve of the core. Built by university programmers who use that code on campus sites means that when it gets to the regular user it seems very solid. We list over 400 courses per week in the dynamic-calendar section and have over 150 pages of static-like pages and phpwebsite is rock solid. At the time i was setting this up Typo and Mambo were the two other CMS's I was considering but the community sites were overwhelming, and the pace of development seemed way to aggressive. PHPwebsite, not perfect, not the fastest loader, not a huge community, not hugely reciprocal, but the coding is rock solid, the quirks can be worked around, and revisions don't bust your whole site. It hasn't imploded on me yet, that is my biggest endorsement.
|
|
PHPWebsite was my first CMS about a year ago when i first decided to build my own site. It was relatively simple to set up and administer however i found the performance a little slow and eventually i decided to move over to Mambo then finally Joomla which my site now successfully runs under. I also found the available templates lacking for phpws, whereas joomla/mambo there are numerous free and commercial good ones around.
|
|
Contrary to prior post, content blocks are easily moveable. You need to go into Control Panel > Administration >Layout Admin and then enable 'Move Boxes'. Doesn't get much simpler than that.
|
|
The content blocks in this CMS seem to be unmoveable and you can't specify where they should go. Many of the admin tools are counterintuitive or missing common sense functionality. There are no other default themes besides the yellow one which seems to add to the overall frustration level. I would definitely suggest Drupal or e107 until this one gets better control mechanisms.
|
|
|
|
|
|
|
|
|
|
