News
I used to have the CVS version of PostNUke running, but the upgrade failed. So, I bit the bullet, deleted the tables in the database, deleted all the files, and did a clean install. The error is:
Warning: Failed opening 'language//global.php' for inclusion (include_path='') in /home2/www/deathstarinc/html/includes/pnAPI.php on line 369
Warning: Failed opening 'themes//theme.php' for inclusion (include_path='') in /home2/www/deathstarinc/html/includes/pnAPI.php on line 900
Warning: Failed opening 'modules//index.php' for inclusion (include_path='') in /home2/www/deathstarinc/html/index.php on line 120
Which looks like the php can't read data from the database. Anyone know what's wrong? Any tests I can do? Thanks!
emperor@deathstarinc.com
Footnote: 1
I was reading through the system documentation and they seem to be a little behind with the new release... also all documentation ends with the FAQ section - the documentation seems sparse and incomplete... Documentation should be less geeked and more geared to the nontechnical user... also, for the module developers, shouldn't there be some variable definitions, how to's (how to call someone's name, avatar, etc...) it all seems rather cryptic... This to date seems to be the biggest stumbling block for postnuke is the lack of readable documentation... I love postnuke and hope to see it continue to grow and be a killer system
Also an observation I made...
When you see the user login block on the postnuke site and the subdomains for blocks and themes, you see the "remember me" checkbox option. However on the mods.postnuke.com site that option is not available.
Does anyone know if that is a feature that the admin can set for that block or is it a bug of the system?
Richard Wing
On server1, I want to run 4 different PN sites without having to have that many installations to limit upgrade hassles. The sites would share some data, but not all. Mostly users would be shared and I'd like to have different themes running.
For server2, My second question is can I install PN on one server and have it running (as a mulitisite) on other servers, or can PN at least pull the data from SQL on one server.
What I'm trying to accomplish is to (hopefully easily) setup PN for author's sites with all of the members and some other select data centralized from my server. Like a reading network.
I'd like to give the authors (people that are complete newbies) access to some of the features of PN (calendar, easy news posting, polls, etc) for their sites, but all of the memebers would be part of my centralized database. Then, no matter which site they found their way to, joining one site would put them in the central database.
That way I could share and control banner space, ads, and other features with the authors able to have their own look, some of their own data, etc.
To make it clear, I want to run a network whereby I control which features & themese appear on each site, give them access via permissions, but save them from the everything but form-based entering. They know nothing of CSS or PHP or SQL, etc...and I know they don't want to!
Does this make sense? Any idea? perhaps this could be accomplished in some way I am not thinking of.
I'm open to all suggestions, hints and clues. Paid or otherwise.
"View dump (schema) of database" for my sql database?
I've tried to find a good expanation for this but have never been able to come up with something the lay person can understand.
In particular if I choose to do a completely "NEW" install of the latest version of PostNuke by wiping everything clean (after backing up of course).
Deleting everything might be by choice or it might be becasue the upgrade went terribly wrong and everything is screwed up.
What is the best way to backup my SQL database with phpMyAdmin? What options do I check off before saving the file. What the F&%^k does all this s#$t mean? PLEASE HELP!!!:
Which one/s do I tic off in the following list of four options? What does this stuff mean?
Add 'drop table'?
Complete inserts??
Extended inserts???
Use backquotes with tables and fields' names????
Save to file... I KNOW WHAT THIS MEANS!!!
And which one of these three items is the best one to choose and why?
-Structure only?
-Structure and data??
-Data only???
Many thanks!
For a better example I run http://www.nitromodels.com and I wanted to create a group called models so I can show advertisement and annoucements in blocks only to that group. I also wanted to create sub site models.nitromodels.com where it will go more in depth about modeling and also show advertisement and annoucements in blocks to that same group. IS this possible now or will it be possible in the future you can email me at mrnitro@nitromodels.com
Footnote: 1
Here's the short list of features that we have been working on, with their proper credits. I wish I could list all of the people that contributed behind the scenes work that went into this release, but my fingers are bleeding from the thought of it.
* Security *
Many of the enhancements in .71 are more for security reasons. Instead of waiting for new reports of security problems we tightened every aspect of PostNuke to fix problems before they arise. Instead of hearing about a new CSRF exploit and releasing a patch, we believe that the script is now very secure against common and uncommon attacks.
*Session -- Jim McDonald: Providing privacy to users is a priority, sessions provides you with a safer way of handling user logins without exposing information through the browser. The plus side of the sessions is this fixes for once and for all many of the security issues that could arise with the use of cookie's controlling the user variables. The sessions are safe, and beyond the security, they also give you a higher level of control over the security of your site:
High -- When the session expires so does the user's login.
Medium -- Set the user login to expire in whatever number of days, weeks, months, years.
Low -- User's stay logged in until I believe the year 5000 (hey, we didn't call it low for nothing).
*Improved security -- Jim McDonald (author) and implemented by many, but namely adam_baum: new system for handling user input and automatically protecting sites against the most common PHP and cross-site attacks. Variables are now cleaned from start to finish, which will stop malicious attacks. In addition, data is secured by a one time key when modifications, additions, or deletions are performed in the Admin. This goes even farther into your website protection.
* Performance *
PostNuke performance has been greatly enhanced by optimization of many portions of the codebase. The core has now almost completely undergone the rewrite, with just odds and ends to replace. This rewrite has done away with many of the old legacy code that slowed performance, and created a nightmare for support.
*Improved stability -- Jim McDonald: new core codebase provides far greater stability than any other Nuke variant. Jim is a monster when it comes to code. The API has been developed by Jim to create the consistency throughout the core, modules, blocks and themes to provide better stability and performance.
*E_ALL Errors corrected --PostNuke Team: Errors that slowed performance, and left phantom problems in the codebase have all been corrected.
*Blocks Performance Enhanced -- Patrick Kellum and adam_baum: More optimizations to the core that fall under performance enhancements.
* Administration *
Even with the concentration towards the security and performance, we managed to squeeze in a few features that stick with our roadmap. We made some administration easier for you, now and in the future. Some of these features have been asked for, for a very long time.
*Configuration moved to database -- Hinrich Donner, Jim McDonald(authors) Gregor J. Rothfuss implementation: Site configuration now held in a database table for improved ease of use and speed of access. Also allows modules and plugins to add to the site configuration without the hacking of core scripts. In addition, with the moving of the config to the DB, future upgrades will not mean setting your site preferences again.
*Admin control of themes -- J. Cox: Finally, I have done something to deserve a little credit, even something as small as this. There is now an admin setting to allow users to control their theme or set a site-wide theme for all users through the use of a setting.
*Dynamic User Data -- Gary Mitchell: Allow you to choose what information to be collected on your site. In the beginning stages of development, but is very well integrated into the system. This has been a requested feature from the .5 days. The system allows you to define new fields to collect data from your users. You can deactivate fields as well, so if you have no need for the avatar field, it's pretty easy to remove.
* XML-RPC Integration -- Gregor J. Rothfuss: From the press release:
XML-RPC is enabling technology. It will allow to connect multiple PostNuke Sites together, and build sophisticated functionality on top, like scheduled synchronization of content, cross-site rating systems or in other words, Web Services. With technologies like XML-RPC, PostNuke will move beyond its CMS roots, and become a framework for web applications in its own right.
To get the process started, we implemented support for the Blogger API in PostNuke. This allows you to post to your Site from the comfort of your desktop (no browser needed). You can get a list of Blogger clients here: <a target=_top href="http://www.xmlrpc.com/directory/1568/services/pyraLabsblogger/clients">Blogger Clients.
* Modules *
Quite a bit of work has been done with the modules system. It starts with the above mentioned API, but affects many things. Care has been taken to make modules backward compatible with .7. There may be some slight changes because of our prefix change in the database to pn for all fields, but other than that most modules should work. I know that there has been work on the major message forums, and they should all be release very shortly after this announcement, if they haven't been already.
*New modules system -- Jim McDonald (author) adam_baum (implementation): allows for future versions of PostNuke to be backwards compatible with older modules, no more being stuck on an old version of PostNuke because you use a module which has not been upgraded. Module developers should have plenty of time to learn the new system, but after they are are adapted, there should be no further work to have to get the modules ready for future releases.
*pnHTML -- Patrick Kellum, adam_baum, Jim McDonald: Quite a bit of work has been thrown into the pnHTML to allow modules authors reusable code that is easy to implement. Items such as forms, etc can all now be easily written through the use of pnHTML.
*Modules Developer Guide --Jim McDonald: Unlike usual, we aren't just dropping a new system on the module developers laps and asking for you to learn it by trial and error. Jim has written a full featured guide on how the API works, along with examples in the codebase, such as the template module.
* Ratings Module -- Jim McDonald: By itself, does nothing, but is a tool for module developers to add ratings to content without having to develop new code. Quite a few modules such as these are in the queue for module developers to work with.
* Display *
* Center Blocks -- Jim McDonald: Now the ability to add center blocks in conjunction with left and right blocks. This has been a popular hack for quite some time, and has now moved into the core. Make a block in the center, besides just your standard admin message.
* New default theme -- Vanessa Haakenson, Andy Varganov, Abraham Irawan - Brumie: Three brand new designs added to the install. The default theme is now random, but as always you can choose which theme you would like to display from your admin. All three are very, very, nice, and look very professional.
* Block hiding -- Michael Meyer: An admin configurable selection that gives the ability for users to hide any of the admin-defined blocks if they do not wish to see them. A nice feature that expands what your users can do.
* PHPLive Support -- Sascha Endlicher: Very cool application (free) for PostNuke users only. .71 comes with a block to allow you to enable live support from your website. The system allows you to connect to your users and provide support in real time. Take some time to visit the PHPLive website for more information.
* ML Privacy Statement and Terms of Use -- Michael M. Wechsler: Our legal team has put together some documents that every website should have. All of the documents are ML ready, so if you are running a Multi-Lingual website, then your users should be able to read them in their natural language.
I want to take the time and thank every developer that has worked on the thankless job of bug fixing, support, implementation, and translation. Many hours of hard work has been spent behind the scenes on this release getting everything ready. People like Johnny, Jan Schrage, Antonino Sabetta, Volodymyr Metenchuk, Philippe Belin, Rabalder, Pablo Roca, and so many others are what make PostNuke what it is. I wish I could name everyone that has put forth a large effort for this release, but I am getting too old to remember everyone's name. I ask that you take some time and read the credits file, and even go over the ChangeLog, and go to SourceForge and extend a rating for some of these folks.
I hope that you enjoy this release of PostNuke. We probably are going to have an extended development time for next version, but we will be releasing modules that are changed to the API as we have them ready. In addition, we also might have a little surprise for an interim release before our next major one.
Enjoy!
I will need further help through out this year as my business grows. I am seeking professional technical support, and would like to find out now who I can pay for work when needed. I would also like to interview potential candidates for their work style and ethics before I contract with them.
Since I am a single mother of 3, fulltime massage student, and owner/CEO of two (small) corporations, I am not able to keep up with all the changes in Postnuke as they happen. I also am only moderately computer literate, so I have this strange beast that I don't fully understand on which my internet business traffic is based, and I don't know what to do if something goes wrong.
This leaves me with some problems. I am seeking:
-a professional proficient with Postnuke who can communicate on a regular basis (weekly? Monthly?) about the changes happening on Postnuke and update my site as upgrades and useful modules become available
-troubleshooting and error corrections as needed in functionality issues
-graphic design and development
-tutoring/training on website management
If you can address any of these issues, or know someone who can, PLEASE email contact name, address, phone #, rates/range of services, and sample contracts, if available.
Thank you for taking the time to read and considering this request.
Sincerely,
Annebritt Birkeland
Owner
Mountain Waters Spa