Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#1 2011-02-12 15:43:30

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

[wiki] User Doc / Wiki Plugin Documentation

Just ran across a couple of items in the wiki’s plugin documentation.

The first is a house keeping issue. A number of the links to plugins below are broken. Several because the sites are gone/down.

  • Should the links be removed?
  • Or the plugin entry?
  • Is this section going to be maintained or is the new Textpattern.org going to be the hub for all things plugin?

Also:

ied_hide_in_admin has this prominent warning: Warning: This file may contain malicious code, by executing it your system may be compromised.

I guess this is critical, but hopefully in a constructive manner.

I can understand the need for a disclaimer indicating that a plugin is not part of a core install, not maintained by the devs, and even not approved by Textpattern devs.

(Arguably having a process that identifies a plugin as “approved” for use with Textpattern could be a marketing plus)

But the warning as is creates a sense of anxiety about plugins in general, this plugin in particular, and leaves one wondering why on earth a plugin with that potential danger has its own page on the official wiki. (Granted it’s not dangerous, but the page creates that impression). It also would leave one puzzled why a plugin that has been used so much (just google the forums) would have that warning.

It creates confusion. Not a positive imo. But I’m curious for the rationale.

Offline

#2 2011-02-12 16:23:41

jsoo
Plugin Author
From: NC, USA
Registered: 2004-11-15
Posts: 1,793
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Good catch. Last edited in 2006. Worse than useless. I think the page should be deprecated, the list replaced with links to .org and to relevant Wiki pages.

Edit: Didn’t realize the Wiki has the actual plugin code for these plugins. I think it should all be deprecated.

Last edited by jsoo (2011-02-12 16:26:48)


Code is topiary

Offline

#3 2011-02-12 16:45:18

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Since the pages are locked, I presume one of the wiki admins needs to make the changes?

Once the appropriate content is moved to Textpattern.org do we delete the deprecated info from the wiki (or is there a sufficient reason to keep it?).

Offline

#4 2011-02-12 16:50:35

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Plugin files hosted @ the wiki and whose links are invalid.

Last edited by maverick (2011-02-12 16:56:32)

Offline

#5 2011-02-12 16:58:30

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: [wiki] User Doc / Wiki Plugin Documentation

I added the ‘deprecated’ warning to the alphabetical and ‘by purpose’ plugin pages. I guess it’s best if I add it to the individual plugin pages as well?

Offline

#6 2011-02-12 16:59:24

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

I see there are is a “find duplicates” link. Several of the plugins have duplicates in the wiki. The rationale is?

Offline

#7 2011-02-12 17:00:38

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: [wiki] User Doc / Wiki Plugin Documentation

maverick wrote:

The rationale is?

Search me… Plugins shouldn’t be in the wiki at all IMO.

Offline

#8 2011-02-12 17:02:37

jsoo
Plugin Author
From: NC, USA
Registered: 2004-11-15
Posts: 1,793
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Els wrote:

I guess it’s best if I add it to the individual plugin pages as well?

I agree; let’s deprecate all of them.


Code is topiary

Offline

#9 2011-02-12 17:05:49

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Els – I just checked the ajw_ trio against Textpattern Resources

All three are there, with working download links. Would it be acceptable to remove those pages in their entirety? At least from public display (if there is a way?). Or perhaps change their links to their Textpattern Resources links?

Offline

#10 2011-02-12 17:06:56

jsoo
Plugin Author
From: NC, USA
Registered: 2004-11-15
Posts: 1,793
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

maverick wrote:

Or perhaps change their links to their Textpattern Resources links?

That’s a logical intermediate step, although more work.


Code is topiary

Offline

#11 2011-02-12 17:09:42

maverick
Member
From: Southeastern Michigan, USA
Registered: 2005-01-14
Posts: 976
Website

Re: [wiki] User Doc / Wiki Plugin Documentation

Els wrote:

Search me… Plugins shouldn’t be in the wiki at all IMO.

I agree.

I am for having a one-stop plugin source. I agree with having copies of the plugins hosted there. I agree with having a record of version and min. Txp version requirements. The wiki just doesn’t seem the best spot. Though I understand the “why” when it was done.

Last edited by maverick (2011-02-12 17:10:00)

Offline

#12 2011-02-12 17:48:04

els
Moderator
From: The Netherlands
Registered: 2004-06-06
Posts: 7,458

Re: [wiki] User Doc / Wiki Plugin Documentation

maverick wrote:

But the warning as is creates a sense of anxiety about plugins in general, this plugin in particular, and leaves one wondering why on earth a plugin with that potential danger has its own page on the official wiki. (Granted it’s not dangerous, but the page creates that impression). It also would leave one puzzled why a plugin that has been used so much (just google the forums) would have that warning.

Most of the plugins seem to have that warning. I think we should either remove it (and also remove the links to the plugin files), or change it in order to create a less terrifying (but still urgent) message.
There are really ancient plugins in that list which wouldn’t work with Txp’s current version anyway, so I don’t see much use in keeping the plugin files available.

Offline

Board footer

Powered by FluxBB