NewsPublisher 1.4.1-rc Released

NewsPublisher 1.4.1-rc Released

http://bit.ly/MjQ8va

The new version allows you to present the form fields on custom tabs in the front end and works with the Articles extra.
[ed. note: BobRay last edited this post 14 years, 2 months ago.]

Ah. Here it is, I missed it earlier!

Anyway, to make public something I had mentioned to you via email earlier, I've has some success using a plugin with Evo and QM+ to prevent my QM+ users from accessing the Manager. Users that are only allowed access for the purpose of editing with QM+ but I don't want to get into the Manager are assigned to a group. The plugin is tied to the OnBeforeManagerPageInit event and checks if the user is in this group, and redirects him back to the front-end if he is.

This way only Manager users that can be in both locations can get into the Manager.

It's a really interesting idea. I'm not sure how it would interact with the NewsPublisher user's need for certain Manager actions (though not really in the Manager). It would probably work fine and might come in handy for other add-on components. I don't think NewsPublisher needs that any more.

A NewsPublisher user is, for all practical purposes, strictly in the front end. In order to reach the Manager, they'd have to guess and manually enter the Manager URL.

If they did manage to get into the Manager, they'd be pretty much crippled by the NewsPublisherEditor Policy, assuming that the Manager worked at all for them (I haven't tried it).



------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone: http://bobsguides.com/modx.html

I was trying this one out today, what a great package! Can't believe i havent seen it earlier.

However i do have a quick question.

If set it up according to your instructions, i will have a resource called NewsPublisher. I want the user to be able to select parent.

Basically what i am asking for is an easy way for the user to select a parent where the resource should be created when pressing the link of PublishResource. And maybe also a way for a user to relocate the resurce by selecting another parent id when editing the resource?


Is the best way to include parent, then create a list of parent (programattically or maybe with getresources) then write a jquery function to enter the id from selected item in that list into the parent input field? [ed. note: DesignByWilliam last edited this post 13 years, 10 months ago.]

For those who are interested in how i solved this issue ( Still hoping for a better solution though if there is one ) :

I created a wayfinder call inside the form.
In it i specified a rowTpl chunk:


To &show, i added parent, and that becomes a input field in the form.

Then i just wrote a jquery script, that grabs the data-resource attribute, and adds it by .val() into the parent field.

/w

I'm not sure exactly what it is you're trying to do.

As you probably know, you can just add the parent field to the form and let the user enter the ID of the parent resource in that field.

You can also specify the parent in the NewsPublisher tag, so it's possible to generate the NP tag with a snippet and set &parentid there dynamically.

I don't see anything wrong with what you're doing, though.

What i am trying to do is create a resource with the newspublisher tag, where you can select parent with a better userinterface than just entering an ID. People with no access to the manager would have no idea knowing the parent ID when i have friendly urls turned on.

So what i am trying to do is create a way for them to see the ids together with the name of the parent, making it easier for them to select the id to create the resource under.

I want one newspublisher page for it, not create many. Therefore i believe setting the %parentid wont be of use since i want the user have a better visual interface and have control of where to store the resource.

But i think im on track here and it will work perfectly. Thanks alot for all the hard work on this package!

Is it possible to (without changing the code) make frontpage editable and not be on the noshowlist? Meaning, can it be unset somehow in the button snippet call?

I'm not sure what you mean by "frontpage," but the site_start page and the NewsPublisher page are hard-coded as noShow (sort of). The NP page that's not editable is the one set in the NpEditThisButton snippet property np_id -- so any other page with a NewsPublisher tag on it should be editable.

I hope that makes sense.

Thanks, yes frontpage=site_start. I just uncommented the line in the editbutton snippet. Thanks for the support!