Currently, I think the only way to do it is to run different
Pebble
instances at both of http://www.another
domain.com/blog1 and
http://www.anothe
rdomain.com/blog2.
Simon
On 7/21/06, jc martin <jc poxika.net> wrote:
>
> Thanks Simon. Very helpful.
>
> One thing I tried to do is map a domain name to one of
the blog.
> like :
> www.domain1.com http://www.another
domain.com/blog1
> www.domain2.com http://www.another
domain.com/blog2
>
> I can make it work with aliases and redirects, but
since there is
> no blog url per hosted blog, it then goes back to
> http://www.anotherdo
main.com/... when users manipulate the links.
>
> Any suggestion ?
>
> Thanks anyway for a great product.
>
> JC
>
>
> On Jul 13, 2006, at 3:13 PM, Simon Brown wrote:
> Answers inline.
>
> Cheers
> Simon
>
> On 7/10/06, jc martin <jcpoxika.net> wrote:
> >
> > I'm testing the multi blog setup and it seems
that the blog
> > aggregation page is not
> > a regular blog page (no calendar, ...)
>
> Yes, that's right - it's just an aggregation of the
most recent entries.
> Pebble 1.x had more features in this respect (e.g.
calendar and month/day
> views), but I took them out because (a) nobody used
them and (b) they had a
> serious performance impact on large installations. With
the re-architecture
> of Pebble 2.0 now complete, I may re-add some of them
at a later date.
>
> > Is this controllable ? Where is the template for
this page ?
>
> You can edit *some* properties by logging with a user
in the
> ROLE_PEBBLE_ADMIN role and choosing the Pebble
properties link. For example,
> you can control how many entries show up on the page.
The template for the
> aggregated view is in the _pebble theme and is based on
the default theme.
>
> > Also, I've had difficulties to allow a user to
publish on a private
> > blog.
> > I've had to give this user the role
ROLE_BLOG_PUBLISHER.
>
> That's right - this was introduced in 2.0.0-M3 and is
needed irrespective of
> whether the blog is private or not.
>
> > I've also been confused by the configuration in
two places : the blog
> > configuration of owners, publishers, contributors,
and the
> > individual users role in their .properties. How is
this supposed to
> > work together ?
>
> Think of the .properties files as the security realm,
detailing all of the
> users that have access to the blogs. Each of these
users can be assigned a
> generic role such as ROLE_BLOG_OWNER, etc. In a
multi-blog setup, somebody
> with ROLE_BLOG_OWNER priviledges can do anything a blog
owner can for all
> blogs on that install. Clearly this is not ideal in
many cases. For this
> reason, each blog can state exactly which users are
permitted to be
> owners/publishers/contributors.
>
> I'm planning on introducing some user management
features into Pebble 2.1,
> which will make this a little easier to understand and
configure, but it
> works well for now.
>
> > Thanks.
> >
> > JC
> >
> >
> >
>
------------------------------------------------------------
-------------
> > Using Tomcat but need to do more? Need to support
web services, security?
> > Get stuff done quickly with pre-integrated
technology to make your job
> easier
> > Download IBM WebSphere Application Server v.1.0.1
based on Apache Geronimo
> >
> http://sel.as-us.falkag.net/
sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Pebble-user mailing list
> > Pebble-userlists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pebble-user
> >
>
>
>
------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys
-- and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Pebble-user mailing list
Pebble-userlists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pebble-user
|