Sorry for the double post. Sent to two separate email address which
apparently dump to same place. Neither page I sent from mention it would end
up here. :-(
- Caleb
Our details:
Bloggyland.com offers hosting for pre-installed, pre-configured Drupal
solutions which enable you to immediately publish, administer, and update
your website. And though all of our hosting plans come with many more
modules than a base install of Drupal does, you do not need specialized
training or technical knowledge of programming languages or HTML. If
however, you do prefer to tinker - the ways you can extend and customize
your site are truly endless. Fully dedicated and friendly support.
Ease-of-use if our goal. Please visit us and see our on-site demo.
Our url: http://bloggyland.com/
Please let me know if you have any questions and/or concerns!
Thanks,
Caleb Gilbert
Our details:
Bloggyland.com offers hosting for pre-installed, pre-configured Drupal
solutions which enable you to immediately publish, administer, and update
your website. And though all of our hosting plans come with many more
modules than a base install of Drupal does, you do not need specialized
training or technical knowledge of programming languages or HTML. If
however, you do prefer to tinker - the ways you can extend and customize
your site are truly endless. Fully dedicated and friendly support.
Ease-of-use if our goal. Please visit us and see our on-site demo.
Our url: http://bloggyland.com/
Please let me know if you have any questions and/or concerns!
Thanks!
Caleb Gilbert
Has anyone created a profile field for users' news feeds such that all their
submitted RSS feeds appear in a category in news aggregator?
I submitted a feature request at Profile but maybe that's not the only way:
http://drupal.org/node/74439
Also I'm interested in enabling multiple instances of profile fields for
users-- for instance a URL field labeled "Web Site" that the user can simply
add second or third sites.
Thanks,
ben (maurice) melançon
member, Agaric Design Collective
http://AgaricDesign.com - "Open Source Web Development"
web worker, PowerToExchange
http://PowerToExchange.com - "Of, By, and For Entrepreneurs"
person, People Who Give a Damn
http://pwgd.org - "building the infrastructure for a network of everyone"
Hi Devlist,
I'm working with Green Media Toolshed to set up a system for managing
multiple instances of Drupal on the same server and sharing
information between them.
We're very keen on sharing this and collaborating on it with anybody
who's interested in something similar. I'm trying to figure out which
of these functionalities are too specific to our use-case to be
useful to others, and which the community would benefit from
developing a standardized and well-supported way of doing.
So, I've included a list of our target functionality below. Send
feedback! Especially if you're interested in collaborating on this,
or are working on something similar, or if you have ideas about how
to implement it in a way that will be in-line with Drupal Core's
future direction, or if you think it's crazy and can't be done. If
there is enough interest, we'll set up a Drupal Group to coordinate.
Cheers,
=Tones=
greenmediatoolshed.org
tjones.cc
*****
Green Media Toolshed
Multi-Site Hosting Requirements Document, v0.3
Tim Jones - tim(a)tjones.cc - 19 July, 2006
1. Site management
- Provide GMT admins with a "dashboard" list of all current GMT
websites,
including partner information.
- Automatically deploy new Drupal sites based on site-template
databases,
via web interface.
- Track database, client and domain data for all sites.
- Allow and manage multiple domains/subdomains for each site.
- Manage cron.php runs across all sites.
- Run database queries across all sites simultaneously.
- Manage and synch site filesystems.
(I think this is only relevant if the setup it not using
the Drupal "/sites/foo" convention.)
2. User / Client management
- Users and clients have a many-to-one relationship.
Clients and sites have a many-to-one relationship.
- A user may log in to any site owned by that user's client.
- Users have roles per-client that affect their permissions on
client sub-sites.
- Standard ("Authenticated") users are not shared between sites.
(e.g. for Forums, Blog Comments, etc.)
- Clearly the specifics of this need to be thought through more
3. API
- Modules on a given site should be able to access contextual
multihost information. For instance,
- What client is this site for?
- What other sites for this client are hosted on this system?
- Any other relevant client/group data
4. For the Future:
("Wishlist")
- Taxonomy sharing
- Better mailing lists (possibly og2list?)
- Multisite statistics aggregation
- Other stuff?
Hi,
The current way Drupal deals with delete -- using a confirm page -- is not
a real good one.
Think of it. It becomes a habit very quick to press Confirm, and also "of
course I really want to delete it, that's why I pressed the button". A day
later when you realize that this deletion was not a good idea, you can
almost hear the whining of the computer "but you pressed confirm!". "A
computer is like an Old Testament god, with a lot of rules and no mercy"
-- how does this image mate with the friendly smiling face we have choosen
as our icon?
Chad Philips is working on a patch since last fall which would let Drupal
get rid of these absolutely-not-useful confirm screens and give you a
shiny moment when you find out that your precious content CAN be brought
back from the dead.
It deserves much more attention than it gets:
http://drupal.org/node/35422
Please review!
Thanks,
NK
Hello everybody; Alex here.
I don't want to pester anybody, but I'm still new to the process of
reporting issues and things, so please correct me where I err!
Mostly, I just wanted to draw attention to this:
http://drupal.org/node/75186
I've submitted a patch already, but I'm afraid it's more of a hotfix for
myself than a real, solid core patch.
Additionally, I'm not sure if I did the right thing making the issue
"critical". I think I did it mostly because of how much of a nightmare
it could be for web admins. (I shudder to think how many times this bug
has poisoned my front page without my knowledge!)
Please give me some feedback on the patch. If you all think I'm going in
the right direction, I'd be willing to:
=> Install, test, and patch HEAD
=> Expand the patch to clean up node_operations()
=> Expand the functionality of the admin/node form as described in the
issue.
So, feedback. Yeah. :)
Thanks for your time! ttyl
--
Alex (Malex) Markley
http://MalexMedia.Net/
"I may seem like a hard-boiled detective on the outside, but inside,
I'm full of... organs."
Useless Info:
System kernel: Linux 2.6.14-1.1653_FC4
Reliability: 01:00:02 up 3 days, 2:05, 3 users, load average: 0.16,
0.14, 0.15
Just a note regarding all the cache discussions.
I will be in Portland next week for O'Reilly's Open Source.
If anyone is attending, we can do some collaboaration and testing.
I will be in town Tuesday through Saturday.
- Ken
agentrickard at gmail.com
On 7/23/06, development-request(a)drupal.org <development-request(a)drupal.org>
wrote:
>
> Send development mailing list submissions to
> development(a)drupal.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.drupal.org/listinfo/development
> or, via email, send a message with subject or body 'help' to
> development-request(a)drupal.org
>
> You can reach the person managing the list at
> development-owner(a)drupal.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of development digest..."
>
>
> Today's Topics:
>
> 1. GNOME's CMS evaluation for Drupal (Andy Smith)
> 2. Re: Object caching (Larry Garfield)
> 3. Re: Caching, caching, caching... (Gordon Heydon)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 23 Jul 2006 03:31:29 +0200
> From: "Andy Smith" <andyster(a)gmail.com>
> Subject: [development] GNOME's CMS evaluation for Drupal
> To: development(a)drupal.org, documentation(a)drupal.org
> Message-ID:
> <541901410607221831i320e2153x8aed0777fe7b84a7(a)mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hey folks, GNOME is looking to change to a CMS and since I like GNOME I'd
> obviously like it to choose a very nice CMS like Drupal, however when I
> looked at the page plenty of data appeared to be incomplete, things like
> i18n and such that people have less knowledge about, but maybe some of you
> can fill it in
>
> http://live.gnome.org/GnomeWeb/CmsRequirements/DrupalEval
>
> If you are interested in the GNOME project using Drupal, head to that link
> and give some factual info.
>
> --andy
>
