Support/Comments for frontpage 1.0-beta

OK! I’ve made progress:

Turns out the "assets" directory wasn’t set with the proper permissions (thanks for making sure I checked that). I chmod’d new permissions to assets and all subfolders/files, refreshed my page and it looks like the Styles have successfully taken... Now I only have one problem left:

Well actually, this is more a question than an actual problem... I have users that I want to be able to use this feature to add new Job Postings to our Careers page. The Careers page uses getResources to pull info about the resources and compile them into a list. Things such as: Description Long Title, Page Title, intro text, etc.. The problem I’m seeing is that your awesome package includes ALL the different input fields (some of which are not used for these page types). Is it possible to have different Create/Edit pages for different user groups so that I can edit/limit which form fields they’ll actually see?



Oh Also, I noticed that when you publish something using this package, it doesn’t add a "Published" date to it, which is causing some indexing issues with the order my posts appear in. Is this a known issue or something just wrong on my end?

Looks like of all the packages you installed frontpage is the only one using css, this why it highlighted the perms prob on your /assets directory.

The content of the create/edit pages are in chunks named frontpageCreate/Edit, you can change these as you want but you’d have to change the code in the frontpage snippets if you want different ones for different users.

The published date is a bug, I’ll raise a ticket in github.

Quote from: shamblett at Feb 24, 2011, 10:58 PM

Looks like of all the packages you installed frontpage is the only one using css, this why it highlighted the perms prob on your /assets directory.

The content of the create/edit pages are in chunks named frontpageCreate/Edit, you can change these as you want but you’d have to change the code in the frontpage snippets if you want different ones for different users.

The published date is a bug, I’ll raise a ticket in github.

I’m probably going to be using FrontPage and duplicating the snippets to make about 3-4 different editor pages for different usergroups / documents. It’s a very smooth system you have here. DO you think that if I have multiple frontpage snippets with calls to different Editor pages I will end up with any trouble on my site?

No, you seem to have a good handle on this, you can pull in different frontpage pages dependant on the login using the snippets to presort the user then pull in the appropriate chunks for the edit/create pages
This should be OK, to be generic it doesn’t do this out of the box of course, when you’ve done this could you please post what you’ve done here, it will be instructive to other users as I can put it in the user guide even if I can’t change the code to directly help in this.

Thanks for your work on this.

-I like how I can create new templates that contain my css files to use while editing/creating documents.

Some questions:

1) when I create documents they are being created under root rather than under the parent page (ie. the page I was on when I clicked the ’create’ button). It is suppose to create ’child’ pages of the current page right, or is there something I’m doing wrong? [[*issue on github says this is fixed but do not see it in the latest package of Frontpage I just installed]

2) When I’m finished editing/creating a resource the window how do I close the frontpage window??? I can hit the back button on the browser to do the trick but IDK is there a way to close/cancel Frontpage??? [*saw the issue on github, but no ’cancel’ button on my version]]

3) Is there is suppose to be a ’lightbox’ window that opens? I’m being redirected to the frontpage editing/creating document. (I’ve made sure jquery is loading)

4) can you just make this identical to the old QuickEdit plugin from Evo? kidding

Hi Hlight,

Ok,

1. You need to change this system setting :-

1.default_template. This field dictates how templates are assigned to newly created resources. If it is set to the value ’parent’ newly created resource templates will be set the value of the parent resource if one exists, otherwise 0. If it contains a value then this value will be used.

. No issues in frontpage are fixed yet(non closed), so there is no next version, this is something I must get round to.

2. and 3. There should be a lightbox window with a ’X’ box in the bottom left hand corner that closes it. Have a look at the screenshots for frontpage in the extras section. If its not appearing have a look in yourr browsers dev tools for any page load errors to see whats going on.

He ability to tailor the templates has been commented on before, you can also tailor the form layout be using your own create/edit chunks. This is an area I didn’t really cover in the user guide, silly me.

Hi,

I just installed this as well, and I had some of the above-mentioned install issues, but I managed to figure them out on my own. The problem I have now is that after I login from the front end, I get the bar at the top with the edit and create buttons, but when I click either of these, the loading bar in my browser lights up briefly and the page refreshes, but no toolbars appear. The page looks exactly as it did before. What is wrong and how can it be fixed?

Traditional Revo 2.0.4-pl2
Apache 2.2.17
PHP 5.2.16
MySQL 5.1.47-community-log
pdo_mysql yes
WinXP / Firefox 3.6.15

Excerpts from Error log:

[2011-03-18 11:47:27] (ERROR @ /home2/nepafouh/public_html/core/xpdo/xpdo.class.php : 1754) PHP warning: json_encode() [<a href=’function.json-encode’>function.json-encode</a>]: recursion detected
[2011-03-18 12:03:33] (ERROR @ /index.php) `0` is not a valid integer and may not be passed to makeUrl()
[2011-03-18 12:03:33] (ERROR @ /index.php) [OnWebPagePrerender]<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> ...

Need a german translation anyone?
Here it is: default.inc.php (see attachment)

After installing frontpage, save this file to: /core/components/frontpage/lexicon/de/default.inc.php

Thanks, I’ll raise a ticket for this and incorporate it into the next release.

Just looking for a little input on how to get the tool to work. Anyone? Thanks.