loudlever

WM_SSV – sorry about that. Thought I caught all occurrences of that issue.

I’ve updated the code to solve this problem – version 2.1.3 has the fix.

For reference, the reason why the install would work on one version of your site and not another appears to be related to which version of PHP you are running. This issue was showing up in versions older than PHP 5.4.

Anyway – it should all be fixed now. So sorry for the delay. Let me know if there is anything else I can do to help.

WM_SSV – I’ve fixed the plugin. Please update to version 2.1.2. This should solve the problem you were seeing.

If you have any further issues, please feel free to contact me directly.

Rich

Hey – thanks for the notice.

Can you confirm that you’re trying to activate the plugin on a multi-site WP install? Or are you trying to install it on different WP installations on different site.

I’m having problems recreating this issue and your feedback will help.

You’re not contributing to this conversation.

We have production reasons for not yet running WP 3.2.x.

The shortcode issue I refer to above was how Contact Form 7 changed the shortcode format in 3.x, which requires all places where it’s been embedded to be updated.

Lastly, the enqueing issue is obvious, as the plugin ships with it’s own version of jQuery and doesn’t load the core version.

First, there are several people claiming that the latest version of the plugin is broken in the version of WP we’re using.

Secondly, the shortcode format was changed in 3.x which will require modifying content on every page/post where this form is used.

Third, the enqueing problem (which is what this post is about) does not appear to be resolved in version 3.x.

Is there a version of the plugin that is WP 3.1.x compatible AND fixes the enqueing problem? If so, we’ll upgrade to that version.

Christoph,

This functionality is currently in development. We begin testing the implementation with a few select publishers in early May.

From a writer’s perspective, the submission process will work the same. Simply embed images within your Word doc and HeyPublisher will extract them and make them visible when viewing the work online.

From a publisher’s perspective, the Admin will need to configure the WordPress plugin to indicate whether they wish the images to be hosted on their server on ours (which are powered by Amazon).

If you would like to be notified when this functionality is released to the general public, please send an email to ‘[email protected]’ and we’ll add you to the notification list.

Hope this answers your question,

Richard Luck

Martin – we found an issue when deactivating the plugin. A patch is contained in version 1.3.1 (which should be available on the WordPress site now): https://downloads.www.ads-software.com/plugin/heypublisher-submission-manager.1.3.1.zip

Let us know if you need anything else.

Martin,

We found that we can reproduce this error when ‘deactivating’ the plugin in WordPress 3.0+.

Investigating….

Rich

Martin,

The error message above indicates that the error is being thrown by core. Which version of WP are you running? Are you running WPMU (multi-user) or the stand-alone version?

Do you get the error when accessing the main website, or only when in the admin tool?

If possible, please email me screenshots: [email protected]

Rich

(blush) The plugin truly is the result of a team effort by the Loudlever devs – but I will pass on the kudos. Glad you’re getting use out of our work.

Now – about your comment “does ‘nearly’ everything….” ?? What additional functionality would you like to see?

If you could let us know what else you’d like to see at https://getsatisfaction.com/hey we would really appreciate it.

Cheers,

Richard Luck

Shrikant – I replied to your suggestion on the GetSatisfaction thread you started: https://getsatisfaction.com/hey/topics/customize_accept_reject_review_emails

Rich

Shrikant,

Yes, we eventually plan to monetize the service – but the features that you currently enjoy with the plugin will always be free. In the coming months we will introduce some advanced features (like posting requests for specific articles) that will only be available to licensed users. But we will ALWAYS provide submission management services free of charge.

As for your second question regarding migrating existing users into HeyPublisher: This is a great suggestion. We’ll add that to our development schedule and I’ll let you know when it’s scheduled for deployment. Expect that feature no later than the end of the year.

Let us know if you have any other suggestions. We love to hear how we can make publishers’ lives easier.

Cheers,

Richard Luck
Loudlever, Inc.
[email protected]

Hey – love that you love the plugin and are getting some use out of it.

The functionality that you are describing is coming soon. We’ve had several requests for it. Should be available no later than late November.

In the meantime, our recommended solution is to check that your publication accepts only fiction and map that to an internal genre via the Plugin Options screen. Then put very specific instructions on the page above where the submission form will be displayed, explaining to writers exactly what type of work you’ll accept.

When the functionality you’re requesting becomes available, we will let you know – as well as provide migration instructions.

Cheers,

Richard Luck
Loudlever, Inc.
[email protected]