Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By Dr. DOT on
I am running 6.14. I installed the Domain Access module. I also added one of my sites by creating a domain record. I then built a real simple content page and published to the new site (so I think).
I kept getting 404 errors so I thought I should hop on the server and add a 'drupal' directory to my domain where I am trying to test a page at. I then think I republished the test page.
Now all I get a a blank Directly Listing page in my browser.
Where can I look to read about how to begin creating pages in Drupal / Domain Access?
Thanks.
Comments
_
Drupal nodes (aka pages) are not stored in file system directories but the database. Delete the "drupal" directory you created and go to node/add to start creating pages.
Thanks worldfallz.
Thanks worldfallz. I seemed to be stuck at the same problem (because I'm not really good at programming, I wonder is this the Apache/PHP stuff). I'm using Dreamhost to host my website and they recommended drupal for an easy one-step installation.
Anyway, you mentioned 'delete drupal directory'. my question is, from where do I delete this 'directory'?
Joeyt - adding a "drupal"
Joeyt - adding a "drupal" directory was something I did at the web server level through a telnet connection (yes, kinda Apache stuff). My guess from your comments in your post is that you did not do this and rightfully so, as there is no specific instruction or step that directs you to do what I did.
I had hovered over a link once I setup a new domain and observed that a page might be located in a 'drupal' directory. So I merely took it upon myself to see if creating a drupal directory on my web server for that particular domain had any impact on what I thought I needed to do -- but it didn't.
So let's follow worldfallz recommendation. I have posted forum questions in the past and s/he has responded so I know s/he is an expert user.
Good luck.
BTW, I like your comment from your web hosting company -- "they recommended drupal for an easy one-step installation". Hmmm, it took me over 8 hours to muddle through an upgrade from 6.13 to 6.14 because the readme.txt makes way too many assumptions that you know what your doing in drupal. And now I am into my 4th hour of trying to figure out 'where to go from here'. I believe once I get over this rather large learning curve that everyone warns me about with drupal, that the mud will clear and I will be able to see what the heck I am doing. Seemingly to me, Drupal is like having kids -- you learn the hard way and mess up totally with the first child (who ultimately will require therapy later in life), but you get to do a way better job with kid #2 and then an even greater job with kid #3 -- the one that basically gets to raise himself ;)
Worldfallz... Your post got
Worldfallz...
Your post got me thinking that I should have gone to 'nodes' rather than 'Create Content > Page' which is what I did yesterday that caused me confusion because I could not get past the 404 error.
So I just logged into my drupal install and looked around for a 'nodes' link or path to start creating pages. The only thing I am able to find regarding nodes is:
So how do I get my test pages to appear on my site? The screen indicates they are "published" and I did check the box in the 'Publish to' section for the domain I wanted the page posted too when I created it, and I also selected the domain from the 'Source domain' drop down list.
Now what do I do?
You need to understand the
You need to understand the concept of a node - it's just a piece of content like a page, a blog entry or something. So there's no 'nodes' section to go to.
If you haven't changed much then your published nodes should be viewable at yoursitedirectory/node. Without seeing your install I can only suggest starting again, though I'm sure it's something simple.
There's tons of documentation on troubleshooting, installing etc. but it really is worth the time it takes to get familiar with the concepts first.
Stick with it and the mud *will* clear ...
Seán
Thanks for the reply Seán. So
Thanks for the reply Seán. So I opened my browser and typed www.mydomain.com/node and I get a 404 page not found. Also, I believe I have a fairly good idea on the basic concepts -- that is I do understand the concept of a node and the concept of a module, and a page and a story and so one. The concept I don't quite get is how to get my install of Drupal, specifically Domain Access, to render the pages/nodes/stories I publish. If there are any specific places in the documentation that can help me with this, please let me know. I have searched the doc and Google'd the www and i just can't seem to get the concepts to connect with the underlying system in my Drupal install.
Totally Lost
Ok, now I am completely lost. I have been clicking every link in drupal that I can find to see if something will get me to reveal the pages I have published. I have also Google'd Domain Access Tutorial and read through the README.txt for Domain Access.
Admittedly, I am totally lost.
Does anyone have a tip on how they got started making Drupal work for them?
While I have never used the
While I have never used the domain access module, to find any content saved go to Admin -> Content Management -> Content
I have no problem locating my
I have no problem locating my pages and stories within the Drupal Admin and making any changes to them that I want. It's the serving of the pages (or items from the DB) that is not resolving in my web browser.
As I continue to click around
As I continue to click around within my Drupal Admin, I happened upon the warning message below.
Current Page Breadcrumb -- Home > Administer > Site building > Domains > Edit domain record
Warning Message -- http://www.my_domain.com/drupal/sites/all/modules/domain/tests/200.png is not responding and may not be configured correctly at the server level. Server code 404 was returned.
So I searched Drupal.org site and could not come up with any helpful results. Has anyone ever seen this message? Any suggestions on what is meant by "may not be configured correctly at the server level"?
Further digging is leading me
Further digging is leading me to have to setup the virtual host on my server whereby the document root points to the Drupal location. More to follow as I uncover how to make Drupal work.
_
ok, lets see if we can get you up and running. imo, you're trying to do too much at once. The domain module is one of the more advanced modules-- i recommend disabling and uninstalling it completely and getting core drupal up and running first. http://example.com/node is the core default home page-- if that's not working you have serious problems somewhere and you shouldn't be working on anything else until you get that straightened out. afaik, there's no way that should ever give you error-- unless something is wrong with apache somewhere or you've purposely tried to rewrite that url somehow.
So-- strip down to core modules by disabling and uninstalling contrib modules (don't just delete them uninstall via the uninstall tab on the modules page), verify you have core drupal working at /node, create a few nodes of each content type and lets go from there.
EDIT:
If it's a new installation, it's probably better to start over. And don't use any webhost provide installer (ie fantastico), install it manually.
Thanks for jumping in
Thanks for jumping in WorldFallz.
My core Drupal install works just fine. And I appreciate your comment and advice that I am trying to bite off more that I can chew, so to speak.
The problem is, we manage and maintain nearly 100 web sites. We host them all ourselves. We are a rather large enterprise.
Traditionally we have either had homegrown cms' or have rolled out Adobe Contribute to end users wanting to maintain their own pages. We want to move in a better direction with regards to cms and we want to be able to share content across all of our sites (domains) because at the root core of our site structure, each domain or site is a child with different business objectives and different look & feel. But much of the underlying content needs to be centrally managed and commonly shared on a where needed basis.
So one of the main reasons why I am jumping into Domain Access right out of the chute is that I need to see if Drupal can provide a technology solution to our developers, designers, and end users. I hear that it can and I am told that Domain Access is the module to make it happen.
Since I am a new comer to Drupal, I must admit that the documentation and readme instructions make way too many assumptions that the reader knows his way around Drupal and its base installation. Couple examples -- the doc refers over and over again to the Drupal configuration file. But until you finally make the connection, you don't realize the reference is being made to "settings.php". IMO the doc should state "settings.php" until such time, if ever, that file gets renamed by Druapl to "config.php" or "configuration.php". Also, in the upgrade readme instructions you are told to delete all your files and directories. What you are not told is to leave settings.php behind. The result of deleting everything including the default settings.php file is your sites no longer appear off-line to any visitor. In fact, the pages that resolve allow the visitor to begin to install Drupal once they hit the pages. Nowhere in the Domain Access documentation did I see an instruction that you need to create virtual host entries in your http.conf file. As a SysAdmin I know how to do this, but I ended spinning my wheels for hours trying to figure out why the new domain I setup in Drupal would not resolve. See, because I am not an expert in Drupal at this time, I am relying heavily on what the doc tells me to do.
So far I have walked through installing Drupal, upgrading Drupal, installing modules, creating pages, stories and web forms. I enabled/disabled modules. I've added users and assigned permissions. All of this stuff works fine.
Before I can go any further, I need to be able to tell upper management that Drupal can do what we need it to do. Hence my reasoning for using Domain Access at this point in time.
With all that said, I now understand that in order to get multi-sites working in Drupal, I need to point the virtual hosts to the Drupal install document root. I did not know that until I spoke to someone on the phone yesterday that has already gone down the Domain Access path.
Maybe this post will save someone some time in the future.
_
Ah ok, I get where you're at now. Couple of things-- first, you don't say which instructions you're looking at that aren't clear, however I would definitely recommend giving this feedback to the maintainer (preferably in the form of a patch). Just about every maintainer appreciates documentation feedback-- especially from someone new to their module because it offers a perspective simply not available to someone who wrote the code.
Second, drupal core multisite != domain access. Drupal's multisite capabilities are mostly aimed at running a group of unaffiliated sites off a single code base (mostly for ease of maintenance and upgrades). Though there are some advanced configurations that can enable shared users and content, that's both advanced usage and going to put you out there on the edge.
Domain access, on the other hand, is for setting up and maintaining different domains through a single drupal install. This definitely sounds like what you want, though it too is quite advanced. And there is definitely a discussion of the virtual hosts configuration in the domain access instructions-- i believe it's either in install.txt or install_quickstart.txt. If you can't find it let me know and I'll try to track it down.
Be sure to mention you're using domain access when you seek support-- the way I read this more than likely it refers to core drupal multisite-- I don't remember the particulars about domain access, but again, it is thoroughly documented.
One other thing-- depending on the domain names of the sites involved, you might be able to do this much more easily with the og and/or subdomain modules.
First, the "vague to
First, the "vague to newbie's" instructions relate to upgrading to 6.14. They are the README.txt instructions. I am not sure how to reach the maintainer of these instructions. But you can see a couple posts I made with regards to these instructions at:
I'll try to be more clear about the module I am referring too going forward on future posts. I thought my opening post and most of my ensuing comments mentioned Domain Access, but I'll pay closer attention next time.
Thanks for your assistance WorldFallz