Support/Comments for NewsPublisher 1.0.5-beta1

I can help.

It’s a bug in TinyMCE.

In the file assets/components/tinymce/tiny.js

Find line 170. It should look like this:

Ext.getCmp('modx-panel-resource').markDirty();

Replace it with these two lines:

        var pr = Ext.getCmp('modx-panel-resource');
        if (pr) pr.markDirty();

[[+np.error_[[+npx.fieldName]]]]
    <label for="[[+npx.fieldName]]" [[+npx.readonly]] title="[[+npx.help]]">[[+npx.caption]]: </label>
        <input name="[[+npx.fieldName]]" class="text" id="[[+npx.fieldName]]" type="text"  value="[[+np.[[+npx.fieldName]]]]" maxlength="[[+npx.maxlength]]" />

Actually, the credit belongs to Bruno17, who created the fix, but I’m glad it worked for you. Hopefully, it will be in a new release of TinyMCE soon.

While I have you in a thankful mood, though: http://bobsguides.com/support-this-site.html. I’m hoping to break even this year.

It’s an interesting question. You could try a form customization rule with a constraint set to limit it to that page, but I’m not sure if it would apply in the front end. I kind of doubt it, because I think they’re applied when the Manager form is rendered.

You could move that info into a Template Variable called Location, but that would complicate( and slow down, somewhat) your getResources call.

The only other way I can think of would be to hack the NewsPublisher code.

You’d have to change line 659 of the core/componenets/newspublisher/classes/newspublisher.class.php file from this:

$replace['[[+npx.caption]]'] = '[[%resource_' . $field . ']]';

to this:

if ($field == 'description') {
    $replace['[[+npx.caption]]'] = 'Location']]';
} else {
    $replace['[[+npx.caption]]'] = '[[%resource_' . $field . ']]';
}

I think that would do it, but unfortunately, it would be overwritten whenever you updated the component.

You could hard-code it into the Tpl chunk, but only if that was your only text field -- pretty unlikely.

Hi,

First, I love your plugin. This is as simplistic and as customizable as I could ever have dreamed of for allowing my clients to edit on front-end without worrying about them damaging my templates! It allows me to have multiple calls in different templates/pages to different editors / page creators for different categories. AND The form fields that show up TO be edited can even be altered. Simply amazing, I cannot thank you enough for writing this.

Which is why I am sad to say that I am having a problem Not with your plugin specifically it seems, but with the integration of TinyMCE (Most Recent, installed today) into your plugin. I have all of the settings correct for it to enable the RTE and select TinyMCE, and it shows up properly for Intro Text and Content in the NewsPublisher page where the [[!NewsPublisher]] call is. Alas, none of the buttons are working for things like Bold, Center, Underlines, not even the HTML button to open a purely HTML window.

I’ve tested that the buttons do indeed work on the back-end resource editor when I enable TinyMCE for editing, and I see from the previous posts/discussion that another user confirmed that the buttons were working for him after the "patch". As far as I know, since I installed both of the plugins today, I have the most recent version of both.

Would you be so kind as to search that code-filled brain of yours and perhaps shed some light on my problem? I can’t very much give user/pass accounts to my clients for them to use a RTE that doesn’t, well, do any RTE’ing. Much appreciated for any insight!