Post installation

I have a webpage set up as a web-magazine, and I would like to be able to save nodes as an "issue", but I would need it to be for a user definable period of time.

I see there is a module that does sort of that but it only works for 1 week, does anyone have any suggestions on how to accomplish this ?

thanks

sean

I once changed te picture in the uper left of the homepage but can't find how to do it again after I just upgraded to 4.7.
Also - I have been manually updating the aggragator.....how do I set crontab to auto update it???

Answers in english please as i am only somewhat skilled here.

My site is www.spanc.org

Thankx in advance,

Jeff

I want to create a custom front page for my website that requires users to log in before they can see anything on the site. So far front_page seems to do the trick, however there is a problem with its error page. If a user enter an incorrect username or password, they are redirected to http://wildernessonthelake.org/user/login?destination=front_page to fill their user id and password, which would get an anonymous user inside of the website.

Total newbie here.

I'd like know how I may provide my users the possibility to own/manage an artwork gallery like the one this website has: http://www.terminus1525.ca/studio/view/4407

And when I say how, I'm actually begging for a step by step explanation... pls!

My hobby suddenly got a lt more serious.
It is now my second job, I get paid for it, and now I've been granted my very own dedicated Drupal server for all my present and coming Drupal projects. The catch is that I allso was granted the reponsibility to administer the Drupal isntallation, and keep everything running.
In short: If we get downtime due to Drupal, I get the blame. So I'm going to do my best to allways install the latest security updates, and stay up to date on other issues and vulnerablilities.
To lessen the workload (This is after all a job #2, to be performed after my day job) I'm planning on setting up a multisite setup, with a single codebase, and centralize the basic modules and themes. And thus a number of questions arises:
- How many sites can be run of a single codebase? Are there any limitations I should be aware of (I think I've read something about the cron.php script becoming a heavy dutie script to run if there are too many sites)
- All of my sites are most probably going to have separate databases, is there any way of updating all of them with one single script, when I update the Drupal core. Or is there no way around logging into 20 ish different sites as admin, and run the update.php script.
- I've got absolutely no experience being a server administrator (server admin is not quite right though, I do not have responsibilities for the basic LAMP installation). Are there other issues / problems / challenges I should be aware of when I start running this server?

Hello, I have a question concerning multisite setups from a single codebase. I have several domains served by a single codebase. I would like to set up testing Drupal sites in directories. To explain myself:

sites
        www.site1.com
              settings.php
        www.site2.com
              settings.php

is ok, but I'd like to have Drupal test sites under