Quick Edit-registered user permissions.

ok So Ive created this user...

Editor-

editor group and assigned pages.
I synched it I believe using the web2manager

So this user can log in with the regular web login
and can post a blog post...yeah!

But there is no editcontent ability.

So I trry the same username/password in the manager log in.
almost seems like what I want (though I get that error on redirect) That user can post a blog post and the quick edit feature shows up.

However: when I click on quickedit I get this message-
You are currently logged into the Content Manager. If you would like to close your login session please click the "Logout" button. To go to your startup or home page click the "Home" button.

And no edit capability.
???
there has got to be an easy way to do this. ..

ok I was thinking you could edit on the front end with modx is that nor right? I see you can add blogs on the front end but thats not as in depth as some content. I must be missing a major step-Ive read thru the documentation and I cant get anything to work right.

I just want a user who can add blogs and edit content (like via quickedit) if need be (i.e like a proofreader who adds Pr’s (blog))

argh...I know modx can accomplish what I want to, but i’m just lost I guess.

Quick Edit requires manager users.

Yes finally figured that out..

So I solved the redirect problem (or bypassed it) by using the snippet -ManagerLogin

So thats good...
I see the quickedit now ...But...when I click on it (with this login) it gives me that message instead allowing me to quickedit.

i.e
"You are currently logged into the Content Manager. If you would like to close your login session please click the "Logout" button.
To go to your startup or home page click the "Home" button."


Perhaps a permission issue Im looking into...
TY

Update
I checked the manager user config again...I had set him up to NOT use manager interface. I was thinking this would help if logged in from manager panel. But Ibecause I now bypass that with the managerlogin snippet I set it to "yes" (use interface).

And it seems to be working.

Now I just need to set permissions for blogs and maxigallery (I believe) and I will have a frontend user.
Sorry for babbling so much..perhaps if this works out and I report it it will at least help someone else out too..
(if you’ve followed my mess this far..that is LOL)

Ok I have two managers...and
web2manager capability.
I think I need the latter in order to post blogs as a a manager and still use quick edit. is that correct...or simpler?
:’(

update
ok Here we go here’s my call for what Im using for blogs:

[!NewsPublisher? &folder=`2` &formtpl=`FormBlog` &makefolder=`1` &rtcontent=`tvblogContent`!]

Seems to look okay..so it there must be a permission-document group- manager-web user f@k up somewhere.
right?

I believe at this point I almost have it working but wonder if there is something in the log-in I can do to bridge accounts.

THe user I created:can log in the front end, via the ManagerLogin snippet and is able to edit via ’quickedit’.


THe web2manager seems to create a web user with the same username and password...BUT you have to log in via a standard web user log in in order to post a blog and when thats done there is no quick edit access.

----------------MAJOR UPDATE

Hello, Ive concluded with the help of others that the current user permission system does not accomplish this. Of course, obviously it took me very long to figure this out..LOL!

Anyways I did come up with a work around for now and would like to share it in case you were wondering:
I have at least created users with same
- username and password-(usingWeb2manager snipp)
-and have the Managerlogin snippet set up

So to make it simple for the two editors of this site, they just have to log in separately for blog type posts,
and for what APPEARS (to them) to be front end content editing (its a manager user with restricted access and upon log in does not enter the manager interface). I’ve made a special page where both these logins reside and it seems to work.

At least its not two seperate username and passwords. I think this will suffice for this unusual circumstance.
:)