Deprecated - Drupal core

Why there is no php ?> tag in the end of core files?

Hello,

at the moment i prepare everythin to move from phpnuke to drupal.

but there is one problem, i am using an external forum at the following path www.domain.de/forum/

i think there a some problems, when i put drupal in the root of my server. will it be possible to run my external forum on this path anyway? what can i do that drupal wont be angry.

thanks, regards

Hi

I'm interested in setting up a multisite Drupal install on a set of subdomains, for a company website. I don't mind retaining all the nodes and taxonomy etc throughout the sites, however I would like to customise what is immediately available to viewers via the block / menu system for each site in the multisite setup, and also retain separate statistics / logs. Here are the tentative subdomains:

• www - generic news, plus rss feeds from various sections (eg. forum, ecommerce, blogs etc) leading to the nodes on the respective subdomains. This will essentially be a portal to the rest of the multisite system.
• company - pages of general information about the company. This will be relatively static.
• courses - the company is a certification franchise, so this will be hierarchial group of pages (book) detailing the course branches and individual certifications.
• dealers - this will be linked to another system (I intend to set up a custom module for this) that searches for certification dealers in a different database.
• resources - a document / file repository for registered users.
• community - this will hopefully be the most actively used area of the site, with a forum, user blogs, photo galleries and event calendars.
• store - the ecommerce module.

After taking a look at the Drupal database, I've come to the conclusion that the following tables should be copied and prefixed for each subdomain:

I am looking at adding support for two factor authentication. Rather than replacing the existing authentication mechanism, the second factor would be in addition to the existing mechanism (be it local or a configured external authentication option). I know where in the user.module I would need to modify to do this for my purposes. But that isn't the reason I am writing this post.

My general question is, as I was unable to find any real discussion about it, are there plans in the works to change / modify the way authentication occurs? Right now (as of the 4.7-rc3) tree, it looks like the logic behind authentication is:

1. Check local auth
2. Attempt to guess the type of external auth
3. Loop through each module checking for an _auth hook

Stopping at whichever stage results in a successful login.

Further more, non-local authentication requires the username to be of the forn 'user@server'.

Now, specifically, I recall seeing a discussion about the whole 'user@server' issue being not ideal for things like OpenID, etc. But I can't remember where I saw that discussion. If it is still on going, any pointers would be helpful.

When it comes to authenticating users, I was curious if a "filtered" (or "chained") approach would be considered in the future? Meaning, rather than strictly looping through each module. It would be possible to construct different "authentication filters" that are chained together and a successful login only occurs after each filter is satisfied.

Greetings,

I found that sometimes it is not convinient to have create content links (forum topic, blog entry, story, etc.) to be automatically available for users. All node/add/{node_name} links are used by admin in most cases. So, how to solve the following task in more appropriate way:

I want all node/add/{node_name} links be available somewhere in administer menu and be invisible for users. These users must have an ability to add this content but from within other web pages of the site but not from menu ...

If I understood correctly, Drupal 4.7 is going to be released whenever there are no critical bugs recorded.