johnmyr

Its hard to pick one feature cause there are some features that will take WP to the next level if they are incorporated together:

Custom content types enhancements together with taxonomy enhancements and custom fields enhancements are by far the most important to put into core in my opinion, as it will make WP more usable for sites thats more than simple blogs.

Kjetil:

after I ran into problems, I tried to ask (still on the comments’ page). Maybe because those questions were considered “negative”, they were deleted.

Maybe your questions were deleted as the article your commenting on clearly states:

Please don’t use my contact page or the comments section below to ask support questions. Use my support forums at Theme Hybrid, which is where I handle all support questions for my WordPress projects.

The plugin itself is well documented in the readme.html All info you need is there for free. However with thousands of users some might run into special problems related to their lack of WordPress/PHP knowledge or problems related to server setup or other conflicting code. If so happens theres an option to get personal support for the small fee of 25$.

I am a member on Justins forums and its the best support I have found yet in the WP sphere.

You cant expect a developer with more than 100.000 downloads of free code to give free custom support on his blog. It would clutter the comments on his great articles, and take all his time. I`d rather see Justin make some money on doing custom support and continue to give us great tools and great innovation on how to make the best use of WordPress for free, with stuff like his new great Members plugin and the taxonomy articles.

The business model is great, and its totally in line with what we want in the WP community.

Kjetil – Dette er faktisk den verste posten jeg har sett her inne hittil. ? oppfordre til boikott av en plugin som er s? popul?r og som faktisk er bygd inn i en mengde temaer. Justin er en av de som virkelig fortjener donasjoner. Han gir ut h?ykvalitets plugins som l?ser problemer for tusenvis av bloggere og skriver noen av de beste artiklene som publiseres om WordPress.

En unnskyldning er p? sin plass n?r du blir edru.

Faen til syting da Kjetil. Du tjener jo penger p? WordPress selv. Supporten hos Justin er superb, den beste i hele WordPress sf?ren s? denne gangen bommer du stygt…

Kan jeg f? gratis annonseplass p? Dolcevita ?

@amandato:

New readme.txt proposal: https://www.wptavern.com/forum/plugins-hacks/691-arguing-wordpress-extend-hybrid-bugfix-plugin-vs-hybrid-3.html#post6097

amandato: Justin, I’m truly sorry your taking this as hostile. Once I found out this problem would not be fixed in the Hybrid theme, I coded a solution in my plugin which lead to the creation of this plugin. Please accept it as just that, a plugin that solves a problem.

As stated elsewhere its not the plugin but the readme.txt that is perceived as hostile by me and many others ( including Justin ). If its not the intention to be hostile, then a revised readme.txt will be appropriate in a 0.1.1 upgrade.

There is no need to change the theme cause it has an option to turn the function off if theres plugin incompatibility.

https://www.wptavern.com/forum/plugins-hacks/691-arguing-wordpress-extend-angelomandato-vs-hybrid.html#post5785

Angelo Mandato should change the readme.txt which is perceived as hostile.

@onewalrus

I`d say the negative

Now this takes the cake.

remark is what upsets people.

General questions on inclusion rules and practice would not upset anyone and would be a valid discussion, though the plugin repository is only a hosting subversion repository service for plugin developers and a centralized download service for end-users.

Plugin developers use this repository when developing new plugins reusing bits of code in the spirit of GPL, and even if a plugin have some exclusive use out-of-the-box the code is shared for anyone to modify and build on which is an important freedom ( to paraphrase Matt )

When end-users browse and download plugins from extend, they must always filter out what they actual may and want to use. Lots of plugins have either bad coding, security problems, incompatibility with other plugins or themes, or just doesnt support the latest builds of WordPress.

You`re not getting the heat because you

questioned a club your not a member of

, youre getting the heat because you jumped to a uninformed conclusion:

Now this takes the cake.

, and use demagogic arguments about what Hybrid users consider a great service offered by Tadlock and Automattic/WordPress.

The slip-up with your site and the overwriting of original copyright notice in css didnt make commenter’s more friendly.

I dont really understand the problem.

As long as the plugin states clearly what it supports, and the code it supports are GPL, theres no problem.

Plugins supporting code thats only commercial available or not GPL would be a different story.

The code is up for grabs if someone wants to fork it and make it compatible with some other themes.

Should plugins adding specific functionality to P2 ( Prologue 2 ) or a plugin that adds new functionality to another plugin not be allowed, like the NextGen Gallery addons etc ?

That would be just plain stupid.

Maybe this will be helpful ?

https://www.wooliet.com/2008/09/05/wordpress-jquery-and-noconflict/

Id just like to second jeffr0s thoughts about using BuddyPress. Atm its very hard to collaborate together with others to make WordPress better.

There should be Automattic moderated and initiated workshops to work on specific issues where people might contribute. I`d also like so see a such workgroup for plugins, themes, hacks and graphics.

BuddyPress should be the colloberation environment.

There`s a nice article on Alistapart this week by Derek Powazek – The wisdom of community:
https://www.alistapart.com/articles/the-wisdom-of-community/

I guess it might be the article that initiated this discussion ? ??

John Myrstad

I based my question on the WordPress plugin downloaded at pageflipgallery where the license says:

LICENSE GRANT
Mediaparts Interactive S.A. grants to you, on these terms and conditions, the non-exclusive right and license to use
this Software. The Software is offered under a TRIAL LICENSE and permits you to use this software exclusively
for non-commercial testing purposes and for a period not to exceed 90 days from your first use of the Software,
subject to the following terms and conditions.
Install and use a single copy of the Software only on one internet server (under one domain name) for the purpose
of evaluating the Software’ s features.
This software may not be used for commercial projects and may not be distributed as part of templates.

I guess you distribute 2 versions ?

Its also an issue With NextGen 1.21 and Mailpress 2.01.

From mailpress forum:

the problem comes from nggallery.php

if ( defined(‘DOING_AJAX’) )
require_once (dirname (__FILE__) . ‘/admin/ajax.php’);
else {
require_once (dirname (__FILE__) . ‘/lib/meta.php’);
// 131.856
require_once (dirname (__FILE__) . ‘/lib/tags.php’);
// 117.136
require_once (dirname (__FILE__) . ‘/lib/media-rss.php’);
// 82.768
require_once (dirname (__FILE__) . ‘/widgets/widgets.php’);
// 298.792
require_once (dirname (__FILE__) . ‘/lib/rewrite.php’);
// 71.936
include_once (dirname (__FILE__) .
‘/admin/tinymce/tinymce.php’); // 22.408

the ngg requested call back is in lib/media-rss.php
a workaround could be to delete the line ‘DOING_AJAX’

in mailpress/mp-includes/action.php

but the fix must be done on nggallery ..

This issue is with Nextgen 1.21 and MailPress 3 beta 2 on WP 2.71.

I do like the idea though – a GPL license and some documentation would be great.

John Myrstad

Integrating Scissors in NextGen would be a very nice solution…

https://stephanreiter.info/2008/10/wordpress-plugin-scissors/