On 28.Oct.2007, at 12:30 PM, Andrew Hankinson wrote:

I would imagine this means that everyone would have to be logged in as Site Admin. (UID 1)

now i'm confused.

i usually develop alone but i am pretty sure i've been able to give people the privileges to go to the content while the site is offline. i've given them the role of admin. as long as they log in through /?q=user/login, it's been fine.

/ liza

Hi All,

I have two questions related to this url: http://www.centernetworks.com/jobs/program-manager%2C-social-media

1. In the job node that I use, one of the fields which you can see is city. Can that be used as part of the url - so that the url above would become: http://www.centernetworks.com/jobs/new-york/program-manager%2C-social-media

I used path auto to set the urls to use the jobs subdirectory.

2. When I used 4.7, the special characters in a url were replaced with dashes. Now in this new version, the %2 type stuff appears in the urls. Any way to fix this so the url's are cleaner?

Thanks, Allen

Earnie - thanks for getting back to me. This is what I have in the field box for URL: jobs/[title]

What I want is something like: jobs/[city]/[title]

Is this possible?

Thanks, Allen

Earnie Boyd wrote:

Quoting Allen Stern allen@centernetworks.com:

...

I used path auto to set the urls to use the jobs subdirectory.

How do you have the have the path pattern at admin/settings/pathauto set? If you're using [title-raw] change it to [title]. The default is [title-raw].

Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/

Thanks Earnie - I guess I will keep it as-is.

-- Allen

Earnie Boyd wrote:

Quoting Allen Stern allen@centernetworks.com:

...

Earnie - thanks for getting back to me. This is what I have in the field box for URL: jobs/[title]

What I want is something like: jobs/[city]/[title]

Is this possible?

It would be a nice feature to add CCK support to pathauto but I don't think you can do that currently. If you have City as a taxonomy term you could do jobs/[term]/[title].

Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/

Quoting Dale McGladdery torelad@gmail.com:

...

What I want is something like: jobs/[city]/[title]

Is this possible?

The token module allows the use of additional fields in pathauto. If I'm understanding your setup correctly, it will do what you want.

Do you have a sample of how? Really I tried when I responded. I still don't see how to do this.

Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/

Wow,

Thanks to everyone.

I implemented a combination of my original plan relying on content access, and the front page module suggested by Laura. I couldn't use Front page alone because direct links, possibly reached via search engines, would work.

I like Earl's idea -- really does the same thing as the Front Page module does, but lower overhead since I rely heavily on the Views module anyway. I might switch to that approach.

Thanks Martin for the custom "access denied page" idea. I'll certainly file that away.

Liza (blogdiva) had the simplest idea -- but there's no way I'm giving out the admin login info. I develop using a content/training focused development method where I engage with multiple folks on the client side from the start -- getting them to send content to me via the Drupal installation. From the very first, I'll have them send me docs by having them create a node with a file attachment instead of sending it to me via email. A lot of back and forth that would more naturally happen via e-mail in a lot of developer/client relationships I conduct with a blog or a forum on the developing site. If I need to get feedback on some graphics etc. I'll put the question out as a poll at the site and get the client folks to vote on the site. Some might think this is more work, but I'm passionate about including real training with the development (I charge for it as well!).

Again, thanks for the great ideas.

Shai

shai@content2zero.com http://content2zero.com

On 10/29/07, Earl Miles merlin@logrus.com wrote:

Shai Gluskin wrote:

...

So I'm working with an organization on a site rebuild. I have a test site set up on my domain.

My problem is that the "Welcome to your New Drupal Site" page is showing up on the home page for anonymous users.

I've installed the Content Access module (http://drupal.org/project/content_access) to make it so that the staff and I can all work on the site and the content won't be available to the public till we launch (and change the access settings).

I created a block with permissions set to "anonymous" and display set to "only on <front>"; it displays in the center of the page (thanks to LiteJazz Theme) telling anonymous folks that this is a development page, with a link to the old/live site.

When I (role=webmaster) or staff (role=staff) log in, everything is fine, just like I want it -- the block disappears and all the content appears.

I just want the "Welcome to your New Drupal Site" to disappear for anonymous users.

I tried making the "You are on a test site" a node instead of a block. That makes the "Welcome to your New Drupal Site" dissappear for anonymous users, but the "You are on a development site" node, continues to appear after staff or I have logged in. I've tried in Content Access to just check "anonymous" -- but it seems that module doesn't work the same way as the blocks code does.

Install the Views module.

Enable the 'frontpage' view, and then 'Add' it so you can override it. Set the Empty text to what you want your users to see.

Then go to administer >> site configuration >> site information

Change the 'default front page' to 'frontpage'. This will make the frontpage view the default. The view that ships with Views behaves exactly like the normal Drupal frontpage, except for the 'no content to display' case, so the only difference you'll see is that the page you're talking about will disappear and never be seen again. -- [ Drupal support list | http://lists.drupal.org/ ]

Earnie Boyd wrote:

It does show when the UID is 1 but whether or not that is a bug is left to interpretation of ideas. As Drupal is coded UID 1 should have rights to all data so it isn't a bug but as designed.

This is correct. By design, you cannot restrict UID1 from any content.