Enabling Approver Permissions

[Hoolahawk]

Hi,

I have setup a user and made them an approver. But when I clicked on
"Request Approval for this content item" the next screen displays the
following error message.

"There are no users that have permission to approve all items. Request
approval for items one at a time or manually notify potential
approvers."

I have checked the permission and I can't see what the problem is?

Any suggestions?

Cheers

David

[AJ Mercer]

might take an application reload to pick up the changes
?updateapp=1
or in (v5) webtop Admin tab

--

AJ Mercer
Web Log: http://webonix.net

[Hoolahawk]

Hi AJ and everyone,

I have reloaded the application, restarted the server, cleared the
browser cache' and fiddled with the permissions and I still get the
error message displaying. Not sure what I am doing wrong here but I
can't seem to be able to request approval of a html page for anyone,
frustating :(

Has anyone come across this problem before? Is there anything else I
can do to check etc?

Any help would be very appriecated.

David

[shi...@gmail.com]

What content type are you working on?

Blair

[Hoolahawk]

Hi Blair,

I am working on a dmHTML page, althought this problem seems to be
occurring over all content types. I can approve the content item
myself but not request approval.

On Jul 31, 12:10 pm, shi...@gmail.com wrote:
> What content type are you working on?
>
> Blair
>

[shi...@gmail.com]

Have a look at the permissions on the parent navigation node of the
HTML page you're working on. If you right click on it in the Site tab
there should be an option for that.

Look at the SysAdmin section (or whatever role you're testing with).
Is RequestApproval "Inherit (grant)" or "Grant"? If it is, then this
is definitely a bug that I need to look at :).

On 7/31/08, Hoolahawk <hool...@gmail.com> wrote:
>

[Hoolahawk]

I checked the permissions on the parent node and the were set to
Inherit (grant). Is this a bug or is it something to do with my setup?
I mean that surely this would have been noticed already if it was a
problem?

Cheers

David

On Jul 31, 1:37 pm, shi...@gmail.com wrote:
> Have a look at the permissions on the parent navigation node of the
> HTML page you're working on. If you right click on it in the Site tab
> there should be an option for that.
>
> Look at the SysAdmin section (or whatever role you're testing with).
> Is RequestApproval "Inherit (grant)" or "Grant"? If it is, then this
> is definitely a bug that I need to look at :).
>

[shi...@gmail.com]

A bug probably. I'd appreciate it if you would add a ticket for it.

On 7/31/08, Hoolahawk <hool...@gmail.com> wrote:
>

[Hoolahawk]

Okay I have been doing some work on this problem (?) and I thought
that I would give an update on at least partly on what I think on e of
the problems is.

* In the table (I am using SQL Server 2005) dmProfile the value in the
column "bActive" is by default 0 (zero) for new entries and at
installation.

* If you set the bActive field to 1 (via SQL Server) then this error
no longer apprears and you get "Request approval from" "All Approvers"
checked.

I don't see how the bActive field is set via the webtop CMS back end.
I know you can set the "User status" say to "Active" although this
seem to have no effect, because if you set bActive field back to 0 for
all users then the error appears again.

How do I get the users in the publishers group to appear?

Cheers

David



If you edit the user state of a user and mark them as "Active" this

On Aug 1, 9:33 am, shi...@gmail.com wrote:
> A bug probably. I'd appreciate it if you would add a ticket for it.
>

[Hoolahawk]

Actually it seems that the all the users with the bActive field set to
1 appears as an approver in the list.

Cheers.

[Jeff Coughlin]

David,

I just came across this bug yesterday morning. I tracked down the bug
and submitted it to Daemon (Blair specifically). I should have marked
the bug as a "Show Stopper", but I have a temp work-around that you
can use in the meantime. To my understanding this bug exists for
FarCry 5.0.0 to 5.0.2 (and the current trunk for 5.1). Hopefully a
fix will go out for p500 as well as trunk since it's a show stopper
for all contributors.

For more info on the bug and the temp fix (in the comments) go here: http://bugs.farcrycms.org/browse/FC-1530

Regards,

--
Jeff Coughlin
Web Application Developer
http://jeffcoughlin.com

[shi...@gmail.com]

FYI I believe I have fixed this issue:
- removed check to deprecated bActive flag from request-approval process
- updated getRolesWithPermission function so that it also looks at
type (e.g. News Approve) and object permissions (e.g. Navigation
nodes)
- changed getGroupUsers in FarcryUD to only return "active" users

Since these permissions and some of the components are cached, you
will need to reload your application's security when you deploy the
update.

Also, I noticed that the approvers displayed are filtered by those
that have email addresses.

Cheers
Blair

[Hoolahawk]

Hi Blair & Jeff.

Thanks for looking at and fixing this bug. I am assuming that the fix
will be released in the 5.1 update? Is this available as yet?

P.s. while I have got you on the line so to speak...I just wanted to
say that FC 5 is some much easier to work with compared to FC 3.01. I
was able to setup and get a custom type exactly how I wanted to run in
about 30 min, fantastic. Thank you for all of you effort.

Cheers.

David

On Oct 2, 5:43 pm, shi...@gmail.com wrote:
> FYI I believe I have fixed this issue:
> - removed check to deprecated bActive flag from request-approval process
> - updated getRolesWithPermission function so that it also looks at
> type (e.g. News Approve) and object permissions (e.g. Navigation
> nodes)
> - changed getGroupUsers in FarcryUD to only return "active" users
>
> Since these permissions and some of the components are cached, you
> will need to reload your application's security when you deploy the
> update.
>
> Also, I noticed that the approvers displayed are filtered by those
> that have email addresses.
>
> Cheers
> Blair
>

[Jeff Coughlin]

David,

> Thanks for looking at and fixing this bug. I am assuming that the fix
> will be released in the 5.1 update? Is this available as yet?

It looks as if this fix is only for 5.1 (in SVN trunk).