Appearance/Settings in Self Hosted Enviroment

An export of your Drupal Gardens site will include every element of your theme. However, the ThemeBuilder is an exclusive service available only to sites on the Drupal Gardens platform.

Thank you,

I was looking for the docmentation that mentioned that the ThemeBuilder won't export. I found it at http://www.drupalgardens.com/documentation/site-export

Thank you,

Thanks for letting me know.  

So what is the best practice for changing pages once we leave the drupal gardens platform to self hosted?

If by "changing pages" you mean changing the layout, you would need to do one or both of the following:

1] set up blocks to display in the sidebar of your choice based on blocks visibility of either PATH or CONTENT TYPE.

2] if you need the same block to appear in different sidebars on different pages then use the CONTEXT module.

3] for extreme cases you would need to create a new template file to reflect dramatically different layouts.

If by "changing pages" you mean changing the color scheme or background images you wold need to upload the images to your active theme directory and edit the CSS files to use those images. Colors are edited by changing the CSS styles to reflect new colors.

The regular Drupal forums, Drupal handbook, and Drupal Support on IRC are tremendously valuable for ongoing support as well.

The best, free resource for learning CSS is http://www.w3schools.com/css/default.asp which got me started years ago. 

You are embarking on a quite the journey of learning. Drupal is amazingly flexible. The more you know the more flexible it is! Also check out http://www.w3schools.com/php/default.asp if you're interested in digging into PHP. It is very intuitive and w3schools takes a very logical approach to presenting the information.

Of course, if you want to keep it simple... Drupal can be used as a simple content management system. Man organizations and individuals do this very successfully. 

It's all up to you and what you want to do with Drupal.

Good Luck!

Doug Vann
Gardens Advisory Team

trying to make this page full width

http://cgchs.com/content/area-photos

As Doug says, you are embarking on quite a journey of learning - in this case, learning css.

In your sites/default/themes/mythemes/acq_rehava_new folder, open the file defaults.css.

Look for the the entry starting at line 361

Change the 960 to your required width, save it and reload your site page. You may also need to clear your cache to see the change.

Thanks Tone!

Hit me up in Chicago [You ARE going right!?] for a free beverage of your choice!

hey i wanna go

I'll have to take a rain check on the beverage, Doug. Chicago is a bit of a step from the UK.

Tony

As you probably know, when you export, your original gardens site is not affected. You can go back into the gardens site, make the adjustments you want in themebuilder, save them as a new theme if you want, then export the site again. In the tarball under sites/default/themes/mythemes will be the folders with the names of the custom themes you have created. Upload the folder you want to your sites/all/themes directory. It will be available to you with all of the other themes you had the next time you go into Appearance. If you are not renaming, I would set another theme as default first and remove the old folder before uploading the new folder. It is a surprisingly easy process.

There is another way that I haven't tried that might be easier than that. Zip up the new theme into a new tarball & gz file and then use the add module/theme process. It should eliminate the manual ftp work.

Or having missed the obvious... in Themebuilder you can export just the theme itself, and then put it where it needs to go on the self hosted site per above post.

coming back to this again...

it isnt feasible to export the theme itself because i only want 1 page change.

it isnt feasible to re export the whole site becuase all the changes have been made since oct 2011 are not in the gardens site

i find it completely unreasonable that something that should be so simple to do cant be expalined simply or done simply.  

The inability to make this simle is he main reason why Drupal caant take hold wwith the common client.  My client runs a motorcycle shop and doesnt have a Drupal development staff.  They simply want to make one page full width.  Why is this so hard?

What says you?

Another way to skin this cat in your situation would be to create a path where all pages therein should be full page. Then set each block in sidebars a-b to not appear in that path. When creating new pages, set the alias to the new path, or to simplify for the end user, duplicate a content type and rename it full page etc and set it's default path to the new path. This way all pages in that type would be full page. No theming changes and no additional technical knowlege need for the end user..

Oops! I shoud have tried that first to make sure it works as stated. I knew I was using the process, I just forgot how I set it up. I use this process with either views or simple views, which can have a special path. That might be ackward for what you want to do. You can still manually set the alias though.

what do you mean manuualy set the alias?

u know this is so effing aggravating  why is it so damn difficult to do something so frigging basic

all i want to do is make pages full width for my client.  you guys make it so that we have to effing host with you to keep things the way we want and use the tools

wordpress doesnt do this....joomla doesnt do this

why do u

I have been using drupal (self hosted) & drupal gardens for about 13 months now and I am still learning new tricks. So it turns out you can set a new content type to appear in a special path. It is just not done on the content type creation page as I had thought. It's in the path module configuration.

1. Create a unique content type that is only intended to be displayed full page.
2. Go to configuration and scroll down to the section: Search and Metadata.
3. Click on Url  Aliases.
4. Click the Patterns tab at the top.
5. You will see the default alias for all content types is set to: content/[node:title]
6. Copy that and paste it into the text area for your new full page content type, then change the word content to a unique path where full page content should appear. If you have already set up your blocks, use that same path: yourfullpagepath/[node:title]
7. Scroll to the bottom and click Save Configuration. Now all new pages of the full page width content type will appear in a special path by default.
8. Edit each block that appears on the full width page that should not. By default the radio button is set so the block appears on all pages except the ones you list below. add yourfullpagepath/* to the list and save the block. Repeat for any other blocks as necessary and you should be good to go.
9. Your client can now add a new page of content type: Basic Page (No Sidebars) or whatever you decide to call it, and create the page business as usual, and it will appear without sidebars, with no additional technicalities or headaches for user or site manager. If you should later add new blocks to either sidebar, you will have to remember to add the full page path exception.

You no longer would need to bother with the auto alias, but fyi, to edit the page alias, while editing a page, scroll down and click on the seo tab and uncheck the auto-alias box. This will allow you to enter a different path for a particular page.

i will pay you $50 to do this for me.

I tested this on one of my sites where I was doing it the hard way and verified that it does actually work. Use the contact link on the page below to contact me directly so we can discuss the details of the job (how many content types to give this capability to, how many nodes need converted, access to your site, etc): http://www.eightwheeldrive.com/support