No. I didn't want to hack it unless it was going to be simple. That's not the case, so what I'm after is most recent cvs as long as it is functional with default nuke 6.9. I've got two unique confirmations that this is so, why I've decided to use the most current cvs code (if I can find an archive set up for the same install process I'd have to go thorugh for the released version, I want to be able to upgrade easily to the release code). I can update it with the official 1.2 CPG_nuke release later. I need to set up a place on the team's site where they can view digital photos I'm taking of sketches and things like that from meetings, in between meetings and for reference during meetings (we have access to the school's computer lab during meeting times). That's it. I leave everything default unless I'm forced to change it, it keeps it simple.
My current use for the site is strictly as a central repository for Lego Robolab code that we create during meetings and on off hours, team docs, meeting agendas, forum for posting up ideas and info in off hours, and any other team resource we find will be augmented by incorporating into the site. It's not meant to be used publicly, just for team stuff.
So I'm trying to keep it simple. I'd rather not set up another install of a standalone php gallery I've been using on the old site, preferring instead to go forward using whatever phpnuke compatible modules I can find.
That's all. I'm not trying to do anything contrary to what developers are doing, I'm pretty familiar with the open source community. In fact, I think my archived changelog for what I described earlier will be available as a spreadsheet and a pdf file, due to the slickness of the newest version of openoffice. I'm maintaining a little preintegrated base install of phpnuke at home, and offered to share it (and submit a few bug reports or questions while I'm at it). That's all.
No more, no less, nothing out of the ordinary. Sorry I can't jump into the development stream. You can't imagine how many people have asked me to join dev teams. I can't responsibly fully commit to a dev team because I just don't have the time. But I'm more than willing to send someone anything I've worked on. That's what it's all about right?
Gotta go update the old site (not gonna repoint the DNS until I've got the new site in place and mysql schema brought over and tested), the kids will be off school soon and I have a bunch of stuff I got to put up for them for Thursday's meeting. It's looking like to be installing CPG 1.2 the end of this week sometime, and try to have it ready for them to view stuff I'm going to take pictures of at Thursday's meeting over the weekend.
Let me repeat:
It was just an inquiry, I have absolutely no intention of hacking CPG_nuke 1.2 outside of updating to the newest cvs and release when available. I will report anything that looks funny or buggy, or ask any questions regarding those versions. I don't apply raw code hacks. I only look for complete file replacements or modules that are widely accepted in the phpnuke community. There's just too much stuff going on in the phpnuke and associated communities for me to keep track of it otherwise. That's why I put it in 1.2.x support in the first place. I'm not ever going to run anything but cvs and release versions. If I find I have to hack something to take care of a critical bug, I'll send the bug description and fix to you guys and wait for cvs to be updated, then replace my current version with the fixed one. Otherwise, I really don't care how feature-rich it is or how cool it looks, so long as it allows people to look at pictures that I stick up there and keeps working. Keeping it simple.
Think of me as a well-behaved CPG_nuke 1.2.x alpha/beta tester. If anything breaks on me, it's probably a fairly critical bug as I'm not going to be pushing the module too hard.
-rust
PS here's an example of what I'm doing. This should make it clear what I'm up to. It's really no more complicated than this, and that's the way I want to keep it.
pasted from rust_changelog.txt
All entries are in order of application to base install. Timestamps are from whatever I have on my box, they may or may not be accurate. Path is from my storage directory at home, for my own reference. All archives manipulated with Ultimate Zip v2.7.1.0.
10/29/03
Restored phpnuke/nuke_base_69/PHP-Nuke-6.9.tar.gz 10/13/2003 into phpnuke/nuke_base_69/nuke
Applied phpnuke/nuke_base_69/fix_nuke_bugs/secfix3.zip 10/20/2003 into phpnuke/nuke_base_69/nuke
Applied phpnuke/nuke_base_69/fix_sql_sec/SP-10-9-03.zip 10/20/2003 into phpnuke/nuke_base_69/nuke
Applied phpnuke/nuke_base_69/mod_auth/Approve_Membership2.0-6.9-fix.zip 10/17/03 into phpnuke/nuke_base_69/nuke
Applied phpnuke/nuke_base_69/fix_admin_ug_auth/admin_ug_auth.zip 10/17/03 into phpnuke/nuke_base_69/nuke/html/modules/Forums/admin
Applied phpnuke/nuke_base_69/fix_nuke_sql/69sql.tar 10/13/2003 into phpnuke/nuke_base_69/nuke
tar phpnuke/nuke_base_69/nuke directory and uploaded to blank site
end paste