onepack

Hi Marko,

No I’m sorry to report that it’s still actual. On the page with the chat all jquery breaks like I described up here. I don’t get any real errors but I’m now checking with firebug. Maybe I can find something.

No need to remove. Just a warning message in the upgrade of the new plugin.

(When this plugin is new (see stats) why does it have version number 3.1.9? Of course the developer is free to chose any version number but if he had chosen version number 1 or 0.5 the users of newsletter pro would not have gotten the upgrade message anyway.)

Thank you for your help!

Really need to get back to work now ?? Some Magento and wordpress theme work waiting.

Like I said the newsletter pro plugin update can only be downloaded from his site. So changing the readme.txt will not help people using the original newsletter pro plugin as they will not see this change.

The only one who can prevent issues now is the new-plugin uploader.
Simply put an message in the upgrade notice that it is not the same plugin.

I know it has a different name.
Newsletter is the free one.

Newsletter Pro is the paid version that you can download on Satollo his website after you pay a small fee.

Incorrect. The other plugin’s name could be changed.

How? If you can only upgrade by going to his website and download an upgrade.

Dear Esmi, I appreciate your time and help. I understand that you follow all the guidelines and I will not convince you or change your mind slightly.
I just hope some people read this so it prevents them from upgrading and having a bad day/ week afterwards.
Greetings from Holland!

Pro is an paid upgrade from this very good and popular Plugin (371,034 downloads)
Newsletter

He has 27 plugins made for the WordPress community.

I cannot believe that the new plugin builder has not checked if there were any other newsletter plugins around. He must have seen the Newsletter name and he can easily see that there is an paid Pro version as well.

Paid people can only upgrade by uploading the files so the only one who can prevent an issue with the paid users upgrading and breaking their plugin is the guy from the “new” plugin.

That’s the last thing I want to say about this.

I get your point….. Just want to help people here.
Don’t you agree that the new Plugin should at least warn people with the Paid version not to upgrade in their upgrade message or something like that?

Next to that: It has the exact same functionality as I could read and for me it seems like a Scam.

It is not my plugin I’m just a user of the plugin and I was completely confused when I got the message. There is NO notice that it is not the same as the Newsletter (Pro) that is well known.
I just want to help people out before it’s too late and they press the update link breaking the old plugin.
By the way, when it’s a completely different plugin like you say. How can it be that the Old plugin gets an update message in WordPress?
Is it because they use the same name or because the plugin source code is a copy?

The newsletter Pro plugin has been around for quite some time. The people using this plugin all get an update message in their wordpress what will probably break the original plugin. ( I didn’t choose to test this yet).
In my opinion the new newsletter pro plugin should change it’s name and not the one that has been around for a long time.
Not because of the fact that the old original plugin is in the Repo or not. Think about all the people getting an update message in their WordPress breaking their Plugin and perhaps loosing their subscriber list.

Sorry!! My fault. Ignore the above. I forgot to remove the wp_deregister_script( ‘quick-chat-load’ );

Ok, thanks for the feedback.

No errors to be seen in Firebug or the developer-toolbar in Firefox.
Actually all the jQuery related javascript that is used on the frondend stops working. Not only lightbox but also the font-resizer and toggle functionality. However, other small non-jquery scripts work like normal.

Hello JWplayer? Any comment on this?

In line 202 of jwplayermodule.php read needs to be changed to edit_posts.

$media = add_media_page("JW Player Plugin Playlists", "Playlists", "edit_posts", "jwplayer-playlists", "jwplayer_media_pages");

Greetings!

It is pretty serious when you have a blog and all registered users can access, make, change (delete?) playlists of a blog.

You don’t need to add user controls just make sure by allowing that only content editors and higher can see the menu option to work with playlists.

If user can edit posts -> show this that and else don’t show the playlists.

Because of this major bug I need to stop using playlists. After I found out yesterday I went to check the playlists and noticed that some were changed by users!

But can’t you tell the module to only show playlists when the access level is for instance level_7 ?