headers
Jason Rust | 6 Jan 2004 23:14

A few problems getting it set up

I've been working on getting giapeto up and running from CVS.  I've hit
a couple of small problems.
1. There is a problem when editing the permissions of a page.  I click
on Admin, add permissons to my page, and when I try to update them I
get:
Fatal error: Call to undefined function: updateallpermissions() in
/horde/giapeto/admin.php on line 79
I tried changing $perms to $GLOBALS['giapeto_perms'] and that took away
the error but didn't actually change the permissions.  Only changing the
permissions through the Horde interface actually worked.

2. When I try to add an application block it doesn't ever validate, and
thus doesn't save.  I was able to add a block for klutz because it has
no secondary options, but any other blocks that require an additional
field to be selected (i.e. kronolith) don't pass the validate() method
and thus doSubmit() is never called for them.

-Jason

--

-- 
giapeto mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: giapeto-unsubscribe@...
Permalink | Reply | 2 comments |
headers
Marko Djukic | 7 Jan 2004 00:23
Favicon

Re: A few problems getting it set up

Quoting Jason Rust <jrust@...>:

> I've been working on getting giapeto up and running from CVS.  I've hit
> a couple of small problems.
> 1. There is a problem when editing the permissions of a page.  I click
> on Admin, add permissons to my page, and when I try to update them I
> get:
> Fatal error: Call to undefined function: updateallpermissions() in
> /horde/giapeto/admin.php on line 79
> I tried changing $perms to $GLOBALS['giapeto_perms'] and that took away
> the error but didn't actually change the permissions.  Only changing the
> permissions through the Horde interface actually worked.

ok, i'll look into that. you can also use the horde/admin/perms/ scripts those
work for sure.

> 2. When I try to add an application block it doesn't ever validate, and
> thus doesn't save.  I was able to add a block for klutz because it has
> no secondary options, but any other blocks that require an additional
> field to be selected (i.e. kronolith) don't pass the validate() method
> and thus doSubmit() is never called for them.

last changes to the block logic threw the horde_form block selection out of
sync, working on a replacement, hopefully tonight.

m.

--

-- 
giapeto mailing list
Frequently Asked Questions: http://horde.org/faq/
(Continue reading)

Permalink | Reply | 1 comment |
headers
Jason Rust | 7 Jan 2004 06:45

Re: A few problems getting it set up


> last changes to the block logic threw the horde_form block selection out of
> sync, working on a replacement, hopefully tonight.

Works great now.  Thanks!
-Jason

--

-- 
giapeto mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: giapeto-unsubscribe@...
Permalink | Reply | 0 comments |
headers
Jason Rust | 7 Jan 2004 17:52

A few thoughts on installation

On 2004.01.07 16:20:02 +0000, Marko Djukic wrote:
> if you have time, let me know what your thoughts are... up till now i've been
> mostly on my own installing it... so would be good to hear opinions outside my
> mindset.

Now that I've got it up and running I'm really impressed!  It's exactly
looking for, which is to turn horde into a webpage for the public.  Here
were the thoughts/issues I encountered:

1. It took me a while to figure out that the page.html template could be
customized by me.  Once I figured out that I could edit it easily my
page was able to start taking form.  Specifically, I wanted to get rid
of the blocky menu up top so that it looked more like a homepage.

2. I didn't realize at first that the Page Layout settings were
different than the page.html template.  Once I realized that each page
could be given an arbitrary number of blocks but based on the same
template I was very impressed.

3. It almost drove me crazy trying to get permissions working so that
the outside world could see the main giapeto page.  Once I started
editing the perms via the main horde interface everything started going
smoother.

4. The color of the links for sub-pages are hard to read by default.  I
can change that with a better template, but it would probably help at
some point to have a better default template.  I have a designer working
on a layout design for us now, so I'll submit whatever template we come
up with.
(Continue reading)

Permalink | Reply | 3 comments |
headers
Chuck Hagenbuch | 7 Jan 2004 21:44
Favicon
Gravatar

Re: A few thoughts on installation

Quoting Jason Rust <jrust@...>:

> 4. The color of the links for sub-pages are hard to read by default.  I
> can change that with a better template, but it would probably help at
> some point to have a better default template.  I have a designer working
> on a layout design for us now, so I'll submit whatever template we come
> up with.

That'd be great - thanks.

> 6. You get a page not found when you click on Options.  Plus, I didn't
> want the homepage to have a options icon anyhow.  So, I got rid of it
> with a bit of a hack: unset($menu[0]) in config/menu.php

Taken care of in CVS (including an update to Horde/lib/Menu.php).

> 7. For the life of me I can't figure out how to use the image options to
> change the image.  I upload an image, I go back to edit it, it shows
> these nice options to rotate it, scale it, etc.  But clicking on one of
> them and hitting Update has no effect.  And I can't figure out what the
> Keep Original Image? checkbox does.

Not sure on this one; these worked a while ago in Ansel, but I haven't tried
them in a bit.

> 8. Some of the errors were pretty difficult to debug.  For example, when
> I didn't have permission to the page and tried to view it publicly it
> just said there was a configuration error (seems it would be more
> informative to say I don't have permissions).  The following patch would
> fix that:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marko Djukic | 7 Jan 2004 22:43
Favicon

Re: A few thoughts on installation

wow thanks, great analysis. also, thanks chuck for moving quickly with the
fixes. i'll look at the other remaining fixes this week. definately need to get
the image field to work properly for editing, it's a bug.

btw, look at the hooks file, there's the _giapeto_hook_settags() function which
gets called at the end of the page set up, so you can do even more custom code
and create more horde_template tags without affecting the base horde install.

marko

Quoting Jason Rust <jrust@...>:

> On 2004.01.07 16:20:02 +0000, Marko Djukic wrote:
> > if you have time, let me know what your thoughts are... up till now i've
> been
> > mostly on my own installing it... so would be good to hear opinions outside
> my
> > mindset.
>
> Now that I've got it up and running I'm really impressed!  It's exactly
> looking for, which is to turn horde into a webpage for the public.  Here
> were the thoughts/issues I encountered:
>
> 1. It took me a while to figure out that the page.html template could be
> customized by me.  Once I figured out that I could edit it easily my
> page was able to start taking form.  Specifically, I wanted to get rid
> of the blocky menu up top so that it looked more like a homepage.
>
> 2. I didn't realize at first that the Page Layout settings were
> different than the page.html template.  Once I realized that each page
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kyrian | 9 Jan 2004 16:38
Favicon

Per-page header selection.

Hi All,

Some success with giapeto in the environment I've discussed previously,
but my client has raised a serious concern about Giapeto's
functionality.

The problem is that they use CSS and scripting very heavily on a
per-page basis, and these things have to be at least referenced, if not
included inline in the headers.

However at the moment, Giapeto only allows for a site-wide header file,
and a single site-wide footer file to be included.

Are there any ways around this, and/or is this per-page header
functionality planned for inclusion?

Also, there currently doesn't seem to be any functionality to have a
pre-set template layout (well, layouts), which can be re-used to a
greater or lesser extent, most importantly, a layout that you can call
up in one click for a page, without having to recreate the whole layout
for each individual page. Is this in the works too, etc?

To clarify(?), if you have a site which, for the most part uses the same
LHS, top, and RHS layout, but the middle panel changes each time,
Giapeto as it stands is going to be a PITA to use because you have to
redo the layout for each individual page (and there would be lots!),
rather than just calling up the basic page format in one click.

Apologies if I've just not RTFM'd enough, etc.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Marko Djukic | 9 Jan 2004 18:08
Favicon

Re: Per-page header selection.

Quoting "Kyrian (List)" <kyrian-list@...>:

> The problem is that they use CSS and scripting very heavily on a
> per-page basis, and these things have to be at least referenced, if not
> included inline in the headers.
>
> However at the moment, Giapeto only allows for a site-wide header file,
> and a single site-wide footer file to be included.

not necessarily. you can set individual page templates to pages and they will
cascade down to any subpages until another change is set.

plus, if you want to get real fancy with your own template tags, look in the
horde/config/hooks.php file and insert the _giapeto_hook_settags() function.
this gets called at the end of a page load just before fetching the
horde_template for rendering the page. this means you can either override any
giapeto tags already set or create a bunch of your own custom ones.

so you could have in the giapeto/config/templates/pages/pages.html file for
example:
<link rel="stylesheet" href="<tag:cssfile />" type="text/css">

and in your hooks.php (note off the top of my head so there may be errors!):
if (!function_exists('_giapeto_hook_settags')) {
    function _giapeto_hook_settags(&$template)
    {
        global $giapeto, $page;

        if ($page->getName() == 'products') {
            $template->set('css', 'products.css');
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joe Jenkins | 15 Jan 2004 02:15

Error when attempting to edit a block

When trying to edit a block, the following error is generated:

Warning: factory(/horde/config/../lib/UI/VarRenderer/blockedit_html.php):
failed to open stream: No such file or directory
in /usr/local/lib/php/Horde/UI/VarRenderer.php on line 57

Fatal error: factory(): Failed opening
required '/horde/config/../lib/UI/VarRenderer/blockedit_html.php'
(include_path='.:/usr/local/lib/php')
in /usr/local/lib/php/Horde/UI/VarRenderer.php on line 57

I am using the lastest CVS version of Giapeto, Horde and Framework.

Thanks =D
Joe

--

-- 
giapeto mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: giapeto-unsubscribe@...
Permalink | Reply | 3 comments |
headers
Chuck Hagenbuch | 15 Jan 2004 02:41
Favicon
Gravatar

Re: Error when attempting to edit a block

Quoting Joe Jenkins <joe@...>:

> When trying to edit a block, the following error is generated:
>
> Warning: factory(/horde/config/../lib/UI/VarRenderer/blockedit_html.php):
> failed to open stream: No such file or directory
> in /usr/local/lib/php/Horde/UI/VarRenderer.php on line 57

I can't reproduce this, but try what I just committed to
framework/UI/UI/VarRenderer.php.

-chuck

--
Charles Hagenbuch, <chuck@...>
"Here, I brought some cole slaw. It's made from peeeooople! Just kidding."

--

-- 
giapeto mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: giapeto-unsubscribe@...
Permalink | Reply | 2 comments |

Gmane