Christopher J. Hradil

Your original post was actually quite relevant to WP, in that the fact is, that the WP feeds don’t always behave as we expect them to, I’ve looked into using the google gadgets personally, but it’s not too high on my priority list, it’s likely from my experiance, that we’ll need a “google-gadget” feed plugin to format a WP feed specifically for use with the google gadget API. As I mentioned, I have a number of more pressing projects going on at the moment, but when a client really pushes for it, we’ll get the plugin going, it shouldn’t be that hard, the gadget API is very well documented, and the “out of the box” WP feed isn’t formated to work exactly right with that from what I can tell. If I can come up with a quick solution I’ll let you know.

In a global sense as far as your original post, you posted under the misc. category, and the post is relevent to WP whether you intended it to be or not, since your feed isn’t behaving as you expected it to, and that’s something that we as a community should and will address. From a personal perspective, one of the reasons I’ve moved away from other communities/platforms and became more involved with WP, is that a) the software in general plays very well with others, and b) as a whole, the support and development community are not generally close minded, but rather forward thinking and progressive. So it does dissapoint me somewhat that someone would close your original post since it’s clearly not any violation of any kind, and the topic clearly relates directly to WP. The actual solution to the problem in my opinion will likely be a “google-gadget” feed plugin for WP.

first, check: http://codex.wordpress.org/Template_Tags
then take a look at: http://codex.wordpress.org/Plugin_API

between the template tags and hooks/filters you should be able to come up with something close to what you’re looking for

i would try a fresh install in the new domain, then export the comments/posts/users from the old db, and import into the new one. I’ve noticed some very strange issues when trying to move a running install around, even on the same server.

I just got around to reading some of the followups to the original posts in this thread, and wanted to offer the following in terms of an update –
1) I think the links provided above for integration are very useful, and although I’ve considered using the phpBB cookie for single sign-on purposes, I’ve chosen to use xoops as the “core” framework for a site where i need more functionality than is possible using WP alone.

2) Many other products have either exising ports as xoops modules or have a reasonably well documented method for integrating, including mediawiki, phpBB, of course WP, and many others.

3) the last thing to consider, is how your individual sites will be used, for example on my personal site, i’ve opted to install different software in each /dir which is suited to each area’s purpose/use. the / root of my site runss on WP, since I don’t need that much functionality. the other area’s use xoops, with WP, and other modules as needed, but I view each “area” as a separate site, thus install multiple copies of each package as needed, I’ve done this for a number of clients as well. Sometimes it’s needed, sometimes it’s not. That depends on what you are trying to accomplish specifically. I have two projects that have come up recently, which will each require a large amount of functionality, and so, will likely mimic what i’ve done at http://www.hradil.us – running the root as WP, then each area using the right platform for the section’s purpose as opposed to using either xoops/Wp in the root and trying to hack everything together. The entire sites will still support a single sign on to some extent, depending on the specific content area.

If you look at wordpress.org for example, the “forums” area requires a separate login from the “codex” area, which is fine, and suits the sites functional needs.
same goes for the xoops main site, dev site and docs site.
I think most users are used to sites operating this way, and since a wordpress.org “member” may or may not be interested in access to other specific areas, i don’t think folks mind too much having to sign up more than once.

having said all that, sure in a perfect world, a user could sign up for one of my sites one time, then have access to the areas they need/want with appropriate permissions for each, without needing to sign up more than once, i don’t think that’s practical at the moment, except as i mentioned, in the case of things like xoops “modules” or integration hacks.

another good example is bbpress which runs this forum, one would hope that eventually, the logins can be easily integrated with WP or bbpress becomes available as a WP “plugin”.

on the opposite end, one of the site’s i’m working on will have a developers area, and instead of the typical sign up confirmation email, each user will be admin approved, since they will have access to potentially harm the site itself, we need more control over who can/does sign up and who doesn’t. so, using a single sign on for that site, doesn’t make any sense.

in a nutshell, there are many options available for integration of various products/features, etc. each of us needs to pick what works for us and for each site’s specific situation. as long as we’re using products like WP which is easily customizable, and things like the others i’ve mentioned, just about anything we can dream up is possible.

best…chris

what’s wrong with the XHTML transitional standard ? or XHTML strict for that matter, both of which support/require self closing tags as appropriate.

you’ll need to add a new div before the categories div

i’m not sure what you’re looking for, the link you referenced simply has a list of links in the right column to various blogs/feeds, check the WP docs, it’s easy enough to do that, whether in the sidebar or on a separate “page”.