BrendonKoz

I have a website that will be converted from mostly static PHP/HTML to (hopefully) using ProcessWire. There are still a few things I have to work out (mostly the database-driven aspects to be converted) but this particular website pretty much uses a global site header and footer. Out of around 100 pages there are a handful of pages that have custom CSS and/or JS added to do specific things. Each of these pages' CSS/JS is custom to the page. I've been trying to think of the best course of action in designing the template for this conversion. Many small sites can include the custom JS/CSS in globally included files and rely on caching. On the other hand even if it were cached it's additional KB that wouldn't need to be included on 90% of the site's pages. ProcessWire could be used to include a field for additional code (or additional js and css, respectively separated). I realize this could potentially be an extra hit on query time on the database, but ProcessWire also has some impressive caching, especially with regard to Ryan's PRO Cache. I'm just curious how others might handle this type of situation, and why?

I suppose that does make sense since a DB error would be a non-recoverable system error. I'd actually think that would make more sense in most cases than a 404 - at least if a page is supposed to exist. As for the error template - that was basically what I had in mind, yes. I believe that would be perfect. Thank you all for the feedback and discussion!

Yes, sorry for not being clear. Information to developers/administrators is definitely important! I typically check error logs. I could even understand seeing logged in users of the admin group seeing a more descriptive error message (if desirable in the template) than standard site visitors, but what I'm envisioning is basically a custom error page, except obviously not sending 404 headers. Exactly. A default splash page might be nice, but being able to customize it to your own site's design, as well as to your audience, would make things so much nicer when the unthinkable (database goes down) might happen. ...unfortunately that "unthinkable" issue does happen to us more frequently than I'd like under our shared hosting plan. Having the ability to display a custom designed page would just make the system that more robust.

I guess I did find the proper forum then. I realize that Processwire uses Exception handling to bubble up error reporting. I'd just hope that, even if there's an error handler for database issues that it (somewhere) has a way to implement this change. I'll have to look around, but I don't know if I'll be able to find anything. Wishlist!

Although not frequent, and usually not for very long, databases will experience problems and just not be able to be connected to. An error message of just "Unable to complete this request due to an error. Error has been logged." just doesn't seem too friendly to visitors. Perhaps I just haven't seen this (or discovered how to do it), but if it isn't currently an option (or a hook) for this, it'd be a welcomed thing. (If there is a way to do this, I apologize...it's sometimes hard to come up with the proper search terms to find results.)

Okay, it seems I have some more reading and comprehension to do then. I really don't want a redirect, but after reading yellowled's response it then got me thinking about using a ("clone"?) template that could request a page fieldtype and simply pull all of its information. The only difficulty stemming from that would be requiring users to then manually find the original source to modify the content. ... but somartist might have a slightly nicer implementation (I'll have to look it over more carefully to see what it truly does). I'm about to leave for a 4 hour drive to visit family for an extended weekend, so I have not had a chance to fully grasp every one else's responses, but I wanted to drop in really quickly and say "THANK YOU!" as it not only shows the power of Processwire, but also the strong community support. You're all awesome. Hopefully Monday evening when I get back I can look this over and get a much clearer sense of it all.

The more I read through the API documentation, the more I learn, but the more I also manage to confuse myself at the same time, so I thought it was about time that I just asked my question. I built a very, very simple management system for my site awhile back. I received a request that during development of my system I never thought would happen, but seemed completely reasonable once I saw the request - apparently EECMS also doesn't handle what was requested though, so I didn't feel too bad. I'll try to explain below once I ask the question: Is it possible for PW to handle a single page (item/id) under multiple parents within a site's hierarchy? Example Fictitious Hierarchy 1: HOME - Vacuums - - Wet Vac Cleaning Solutions - - - Super Clean 2000™ - Household Cleaning Products - - Super Clean 2000™ Example Fictitious Hierarchy 2: HOME - Payroll - - Paycheck Schedule by Title - Human Resources - - Titles and Salary Levels - - - Paycheck Schedule by Title So the idea here is that a single page/item ("Super Clean 2000™" and "Paycheck Schedule by Title", respectively) only needs to be created and maintained once, but due to logical association should be found as being related to multiple parents within a site's hierarchy (and appear as though they actually are, in fact, children of each parent individually within the navigational structure). Is it possible for Processwire to handle this sort of thing?