Welcome to Geeklog, Anonymous Thursday, May 02 2024 @ 10:38 pm EDT

Comments for Turning geeklog into a true CMS

Turning geeklog into a true CMS | 4 comments | Create New Account

The following comments are owned by whomever posted them. This site is not responsible for what they say.

Turning geeklog into a true CMS

Authored by: Tony on Friday, January 24 2003 @ 10:34 am EST

Dirk, is right. Your item 1 is definitely addressed by GL2. As for item 2, we have planned for affinitiy relationships. A good example of that is a business with multiple departments. The company may have their own GL2 site and all the departments will have affinity GL2 installations so that you can have the corporate site propogate content down to the departments yet the departments can still customize some of their own content.

However, what I think I hear you saying is you have a bunch of un-related GL sites that you'd like to use one set of code and one database for, right? I don't think this scenario was considered in our affinity model but it probably could. We are still in the planning phase for much of GL2 so we'll take this under consideration.

---
The reason people blame things on previous generations is that there's only one other choice.

---
The reason people blame things on previous generations is that there's only one other choice.

Turning geeklog into a true CMS

Authored by: gHack on Friday, January 24 2003 @ 11:59 am EST

Glad to hear that these two items are addressed by GL2 -- that means that I want to get involved in coding somehow. Can you point me to the information I need to read in order to get started? I've been doing PHP for about 4 years but have not as yet contributed to any open source projects. I consdider myself reasonably proficient as I have built a successful corporate site with user services (www.returnpath.net) and am pretty proficient at using CVS (to the point where I don't see how I ever functioned without it). What I guess I want to know is, how do I get a copy of the current version from CVS, make changes and submit them in a way that they can be considered for incorporation into the core code, make notes, etc.? I don't want to hack away at the version I have if I'm going to end up stepping on someone else's changes... that seems like a waste of time. I realize that there is probably a well-established process for this that I'm simply not familiar with. Familiarize me?

For point #2, you are correct that I have unrelated sites but they each use their own database, I just want to keep them using the same core PHP code and separate out the parts that are specific to each site. Sounds like that is pretty much what you are working on. I tried it with some success, but it became enough of an involved process that I started making mental notes about places it could be streamlined.

Cheers,
Chris

Warning: Javascript required to enable functionality

Post a Comment

Search

Resources

About

Getting started

Support

Development

Topics

User Functions

What's New

Articles last 4 weeks

Comments last 4 weeks

Pages last 4 weeks

Links last 4 weeks

Downloads last 4 weeks