PEAR Bug Search Results

pearweb: Bug 16845 [Open] Bug Change/Comment Notifications Contain Raw HTML

demon dot gene at gmail dot com — 2009-11-29T01:28:17+00:00

pearweb Bug
Reported by ashnazg
2009-11-29T01:28:17+00:00
PHP: Irrelevant OS: Linux Package Version: 1.24.0

Description:
------------
In the bug change/comment notification email, the comment area shows some plain text HTML tags.  It looks like these are the actual HTML styling tags that go around the part of a comment that shows changes in the bug header values.

These HTML tags should be stripped out of these parts of comments when the plain text emails are created.

Expected result:
----------------
------------------------------------------------------------------------

[2009-07-21 17:32:39] ashnazg

-Roadmap Versions:
+Roadmap Versions: 1.4.3

------------------------------------------------------------------------

Actual result:
--------------
(this was a comment from bug #14159)

------------------------------------------------------------------------

[2009-07-21 17:32:39] ashnazg


-Roadmap Versions:
+Roadmap Versions: 1.4.3


------------------------------------------------------------------------

pearweb: Bug 16844 [Open] "Patch Added" Email Is Missing Its Bug Info

demon dot gene at gmail dot com — 2009-11-29T01:19:34+00:00

pearweb Bug
Reported by ashnazg
2009-11-29T01:19:34+00:00
PHP: Irrelevant OS: Linux Package Version: 1.24.0

Description:
------------
The "Patch Added/Updated" email I received for Bug #16586 is completely missing any and all references to the bug itself.  Therefore, it's subject is incomplete, and all its hyperlinks are incomplete.

Expected result:
----------------
subject	[Patch] Patch Added/Updated for bug 16586

	
Dear maintainer,

The following patch has been added/updated for bug #16586:

Bug Package: XML_Serializer
Bug Summary: namespace duplication
Patch Name:  add-firstcall-check-to_createXMLTag
URL:         http://pear.php.net/bugs/patch-display.php?bug_id=16586&patch=add-firstcall-check-to_createXMLTag&revision=1259260750&display=1
Date:        2009-11-26 18:46:15

View bug report at : http://pear.php.net/bugs/bug.php?id=16586

Actual result:
--------------
subject	[Patch] Patch Added/Updated for bug

	
Dear maintainer,

The following patch has been added/updated for bug #:

Bug Package: XML_Serializer
Bug Summary:
Patch Name:  add-firstcall-check-to_createXMLTag
URL:         http://pear.php.net/bugs/patch-display.php?bug_id=&patch=add-firstcall-check-to_createXMLTag&revision=1259260750&display=1
Date:        2009-11-26 18:46:15

View bug report at : http://pear.php.net/bugs/bug.php?id=

pearweb: Bug 16747 [Open] Broken license links

till at php dot net — 2009-10-29T01:26:10+00:00

pearweb Bug
Reported by till
2009-10-29T01:25:04+00:00
PHP: Irrelevant OS: n/a Package Version: 1.24.0

Description:
------------
http://pear.php.net/packages.php?catpid=14&catname=Mail

The links behind "PHP" lead to http://pear.php.net/PHP. 
There's another one (on "Database"), where "PHP License" 
leads to another 404. Maybe the default should be, no link. 
The only that links that work are behind "PHP 2.02" and "PHP 
License 3.01".

Others such as "BSD/PHP", "New BSD" are not parsed at all.

(Just btw, that page looks really, really nice!)

pearweb: Bug 16671 [Open] Entire Comments Frame is in Description Box

demon dot gene at gmail dot com — 2009-10-19T02:19:01+00:00

pearweb Bug
Reported by ashnazg
2009-10-02T14:22:35+00:00
PHP: 5.3.0 OS: Linux Package Version: 1.23.2

Description:
------------
On Bug #4197, the entire comments frame (all comments plus the page footer) are included in the Description box.

http://pear.php.net/bugs/bug.php?id=4197

pearweb: Bug 16627 [Assigned] HTTP_Request2 not shown in "most popular", "latest" docs not linked

borz_off at cs dot msu dot su — 2009-09-28T07:41:02+00:00

pearweb Bug
Reported by avb
2009-09-20T12:07:27+00:00
PHP: Irrelevant OS:  Package Version: 1.22.1

Description:
------------
I did a release 0.4.1 of HTTP_Request2 package a few days ago, there are a couple of problems with it on PEAR website
  * It doesn't show up in "most popular" packages, while it should do with 460+ downloads in 7 days
  * 'latest' API docs still link to 0.4.0, while 0.4.1 docs are already online.

Test script:
---------------
http://pear.php.net/feeds/popular.rss
http://pear.php.net/package/HTTP_Request2/docs/latest/

Expected result:
----------------
HTTP_Request2 among "most popular" releases
Docs for 0.4.1

Actual result:
--------------
No HTTP_Request2
Docs for 0.4.0

pearweb: Feature/Change Request 16566 [Assigned] Usability: Add a 'reset password' / other actions to bug error messages

muell at bruechner dot de — 2009-09-09T23:19:10+00:00

pearweb Feature/Change Request
Reported by muell
2009-09-02T17:48:43+00:00
PHP: Irrelevant OS: Windows Package Version: Unknown

Description:
------------
ERROR:

    * Email is already in use for an existing account


Test script:
---------------
When I click "Add Comment" to add a comment for a existing bug, and enter my email adress. Or when I try to add a new bug, like this.

Expected result:
----------------
that there is not such a result.

Actual result:
--------------
ERROR:

    * Email is already in use for an existing account

This happend even when I tried to add   T  H  I  S   bug. Argh!!!!

pearweb: Feature/Change Request 16401 [Open] show a count of comments next to proposed packages in pepr.

daniel dot oconnor at gmail dot com — 2009-07-03T04:31:20+00:00

pearweb Feature/Change Request
Reported by doconnor
2009-07-03T04:31:20+00:00
PHP: Irrelevant OS:  Package Version: 1.21.1

Description:
------------
(12:50:14 PM) gauthierm: CloCkWeRX: another pearweb suggestion: show a count of comments next to proposed packages in pepr.
(12:51:53 PM) loopie [coco@host241-150-1-58.bc-centralplus.com] entered the room.
(12:55:00 PM) CloCkWeRX: i can has feature request for that so i don't forget?

pearweb: Bug 16343 [Verified] Latest pear depends on 5.1.6 but only says 4.4.0

darren at dcook dot org — 2009-06-20T19:39:44+00:00

pearweb Bug
Reported by darrencook
2009-06-18T10:42:28+00:00
PHP: 5.1.4 OS: linux Package Version: 

Description:
------------
http://pear.php.net/package/PEAR/download/All

says php 4.4.0 is the requirement, but it won't upgrade with php 5.1.4.
The reason is only hidden in the release notes for 1.8.0alpha1, where it says "PHP 4.4 and 5.1.6 are now the minimum PHP requirements"

That information needs to be in the requirements section for all 1.8.x versions, not just alpha1 !!

pearweb: Bug 16252 [Open] Adding a new bug report with the wrong db driver = error

daniel dot oconnor at gmail dot com — 2009-10-19T02:20:01+00:00

pearweb Bug
Reported by doconnor
2009-05-23T17:02:28+00:00
PHP: 5.2.9 OS:  Package Version: CVS

Description:
------------
Direct calls to mysqli_last_insertid are being done, instead of trusting the DB abstraction layer.

Test script:
---------------
1. Add a dsn of mysql://foo:bar@localhost/pearweb in
2. Add a bug report

            /*
            * Need to move the insert ID determination to DB eventually...
            */
            $cid = mysqli_insert_id($dbh->connection);

Expected result:
----------------
No errors

Actual result:
--------------
Warning: mysqli_insert_id() expects parameter 1 to be mysqli, resource given in /home/clockwerx/pear-cvs/pearweb/public_html/bugs/report.php on line 310

pearweb: Bug 16236 [Open] Unit tests fail: pear_rest

daniel dot oconnor at gmail dot com — 2009-05-18T16:10:26+00:00

pearweb Bug
Reported by doconnor
2009-05-18T16:10:26+00:00
PHP: 5.2.9 OS:  Package Version: CVS

Description:
------------
Failed unit tests everywhere :(

Test script:
---------------
pear run-tests -r tests/pear_rest/

Expected result:
----------------
Tests run, pass

Actual result:
--------------
Most tests fail with:

Warning: Missing argument 2 for pearweb_Channel_REST_Generator::__construct(), called in /home/clockwerx/pear-cvs/pearweb/tests/pear_rest/setup.php.inc on line 13 and defined in /home/clockwerx/pear-cvs/pearweb/include/pear-rest.php on line 9

Notice: Undefined variable: db in /home/clockwerx/pear-cvs/pearweb/include/pear-rest.php on line 14

pearweb: Bug 16088 [Open] wrong open bugs count when unconfirmed or spam report

pear at laurent-laville dot org — 2009-05-24T15:05:09+00:00

pearweb Bug
Reported by farell
2009-04-11T08:38:02+00:00
PHP: Irrelevant OS:  Package Version: Unkown

Description:
------------
Following my chat with Helgi on PEAR webmaster list 
http://news.php.net/php.pear.webmaster/6502

I open this new bug report about user information page and number of open bugs.

When there is an unconfirmed bug report (or as it was in my case) a presumed spam report, we should not see the number of open bugs increased by these pseudo false reports.



Expected result:
----------------
Number open bugs : 1

For report #15674 only

Actual result:
--------------
Number open bugs : 2

#15674 + #16080
Before I declare #16080 as spam

pearweb: Feature/Change Request 15992 [Verified] Header in bug tracker emails should only contain current values

wiesemann at php dot net — 2009-06-07T07:35:16+00:00

pearweb Feature/Change Request
Reported by wiesemann
2009-03-08T11:54:07+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
The header part of the bug tracker emails should only contain the current values of Status/Type/Version/Summary etc. because the differences between old and new values are now listed in the comment section. The current implementation is redundant.

pearweb: Feature/Change Request 15853 [Assigned] Better format for RSS feeds from bug system

daniel dot oconnor at gmail dot com — 2009-06-30T01:06:26+00:00

pearweb Feature/Change Request
Reported by doconnor
2009-01-31T22:00:58+00:00
PHP: 5.2.6 OS:  Package Version: CVS

Description:
------------
If you subscribe to the bug system's rss feeds from a search result, the feed is badly presented in readers (whitespace is ignored, for instance in google reader).

It should be easy to render out html or something else in the feed which fixes this.



Expected result:
----------------
Readable output

Actual result:
--------------
"Description: ------------ It expects $this->_metaHttpEquivResponse to be an instance of HTTP_Request, but it's actually the value of $request->getResponse() Test script: --------------- $yadis = new Services_Yadis('https://me.yahoo.com'); @$yadis->discover(); var_dump($yadis->getUserREsponse()); Expected result: ---------------- [HTML from request] Actual result: -------------- bool(false)"

pearweb: Feature/Change Request 15399 [Open] Add column "Closed since last release" to bug statistics overview

troehr at php dot net — 2009-06-14T06:46:03+00:00

pearweb Feature/Change Request
Reported by troehr
2008-12-26T12:26:30+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
Please add a new column to http://pear.php.net/bugs/stats.php to display the tickets that have been closed since the last release. This makes it easy to identify packages that may need a new release because a lot of issues have already been fixed in CVS.

Maybe #15393 should be fixed first.

Thanks,

Torsten

pearweb: Feature/Change Request 14973 [Open] easy api doc acces

cweiske at php dot net — 2009-06-14T06:44:49+00:00

pearweb Feature/Change Request
Reported by cweiske
2008-11-07T08:11:56+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
It would be very helpful if one could easily type in api doc urls like
pear.php.net/classname::method
pear.php.net/classname::$var
pear.php.net/Packagename/classname

pearweb: Bug 14666 [Verified] [code=php] is broken

till at php dot net — 2009-08-10T10:56:04+00:00

pearweb Bug
Reported by till
2008-09-19T05:11:47+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
When I use [code=php] in my proposal's description, it wraps the PHP code with  tags, but it doesn't prettify the code (e.g. syntax highlighting, proper spacing).

Test script:
---------------
Use the following code to try it:
http://www.friendpaste.com/H7ULHnvJ



pearweb: Bug 14588 [Open] bug not submitted after confirming email
sandro_berg at gmx dot de — 2008-09-03T03:08:21+00:00
pearweb Bug
Reported by sberg
2008-09-03T03:08:21+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
When I first tried to submit a bug, I got a message that my bug would be made public when I confirmed my E-Mail address. I did so but the bug never showed up in the tracker. Either the message is misleading or the bug should have been sent.

Test script:
---------------
Steps I took:
Without an account, I entered a bug with a patch.
I then confirmed my E-Mail as requested by visiting the Link sent in the E-Mail.

Expected result:
----------------
The bug should have been submitted or the message should have stated that I'll have to resubmit it.

Actual result:
--------------
The bug didn't show up in the tracker.


pearweb: Feature/Change Request 14372 [Open] Better explain "How do I contribute" via pearweb
daniel dot oconnor at gmail dot com — 2008-07-26T08:35:26+00:00
pearweb Feature/Change Request
Reported by doconnor
2008-07-19T07:05:33+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
We aren't gaining enough developers quickly.

We should examine how pearweb can help us do that.

From IRC:
(9:31:52 PM) CloCkWeRX: what's the process-flow from pear.php.net?
(9:32:47 PM) CloCkWeRX: ie, i click into 'developers' and i don't have a "How do I contribute" link / also there's no wonderful button in the bug tracker which converts an outside to a pear dev.
(9:32:48 PM) bentob0x left the room (quit: Read error: Connection reset by peer).
(9:33:16 PM) helgi: mm yes how do I contribute would be a good link in developers


Test script:
---------------
Log in to pear.php.net
Try to find out how to become a developer/contributor

Expected result:
----------------
It's easy

Actual result:
--------------
It's not


pearweb: Feature/Change Request 14192 [Open] ability to add a note when drop a release
pear at laurent-laville dot org — 2008-06-19T12:19:19+00:00
pearweb Feature/Change Request
Reported by farell
2008-06-19T12:19:19+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
I would like to have ability to add a note (reason) about a release dropped.

For example : yesterday (2008-06-18) I've published/uploaded the version 1.8.0b4 of PHP_CompatInfo.

Just in time, I've realized that I've forgotten two package tasks file replacement and 1 dependency.

So, I've dropped the recent upload release, before to reload it again: but as no reason could be given
All users have seen two announcements about PHP_CompatInfo 1.8.0b4 on the PEAR General Mailing List


pearweb: Bug 14132 [Assigned] orphan note management
philip at roshambo dot org — 2008-06-29T05:36:27+00:00
pearweb Bug
Reported by philip
2008-06-12T12:11:47+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
User notes become orphans when the manual pages change. For example, the following note:

 http://pear.php.net/notes/admin/view-note.php?ajax=no&status=yes¬eId=7255

Is associated with:

 http://pear.php.net/manual/en/installation.cli.php

But that page moved.

There needs to be a method for managing orphan notes (to move them). Here's an example orphan note system (for the PHP manual):

 http://doc.php.net/php/orphan_notes.php


pearweb: Feature/Change Request 14018 [Open] Packing Rating with Comments
jeichorn at JoshuaEichorn dot com — 2009-07-24T10:43:37+00:00
pearweb Feature/Change Request
Reported by jeichorn
2008-05-29T16:07:15+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Add a simple 5star package rating system to the website something like the rating system on cpan
http://search.cpan.org/dist/SVN-Notify/
http://cpanratings.perl.org/dist/SVN-Notify


pearweb: Bug 13985 [Open] Doc bug mails sent out before confirmation
bjori at php dot net — 2008-05-27T11:39:16+00:00
pearweb Bug
Reported by bjori
2008-05-25T07:16:11+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.17.1

Description:
------------
(No idea if the package version is correct, didn't get "don't know" option..)

When filing bug reports user has to confirm his email address before the bug reports is visible online. However; The bug report is sent out to the mailinglists (at least pear-doc@) without any confirmation hence defeating the whole purpose of the spam system.


Test script:
---------------
http://news.php.net/php.pear.doc/
10791
10792
10793
10795
(Intentionally not linking)

Expected result:
----------------
Only confirmed bug reports to be mailed to the mailinglists.

Actual result:
--------------
All bug reports are mailed to mailinglists, before being confirmed.


pearweb: Feature/Change Request 13814 [Open] Mail reminder about open bugs need to be clarify
pear at laurent-laville dot org — 2008-05-01T07:01:33+00:00
pearweb Feature/Change Request
Reported by farell
2008-05-01T03:55:40+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
As I've just received the mail reminder about open bugs, I think that you should clarify/classify open bugs and requests , with a new column info (bug Type)


Bug, Request, Doc


Expected result:
----------------
Perharps content like this


Mail content:

 PEAR Bug Database summary for PEAR_Info - http://pear.php.net/bugs

  ID  Status     Type      Summary

13741 Open     Request  show list if potential config files. 

  Further comments can be seen at http://pear.php.net/bugs/13741
  Edit this bug report at http://pear.php.net/bugs/bug.php?id=13741&edit=1


Actual result:
--------------
Mail subject:
[PEAR-BUG][Reminder] Reminder about open bugs in PEAR_Info

Mail content:

 PEAR Bug Database summary for PEAR_Info - http://pear.php.net/bugs

  ID  Status     Summary

13741 Open      show list if potential config files. 

  Further comments can be seen at http://pear.php.net/bugs/13741
  Edit this bug report at http://pear.php.net/bugs/bug.php?id=13741&edit=1


pearweb: Feature/Change Request 13622 [Open] xml/csv export of bug numbers
cweiske at php dot net — 2009-09-08T08:29:19+00:00
pearweb Feature/Change Request
Reported by cweiske
2008-04-08T07:55:25+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
The bug statistics page should get a csv or xml output, so we can make graphs over time and so.


pearweb: Feature/Change Request 13621 [Open] main pages for packages should link back to their proposals
ken at linux dot ie — 2008-04-08T07:51:36+00:00
pearweb Feature/Change Request
Reported by kguest
2008-04-08T07:51:36+00:00
PHP: 5.2.3 OS:  Package Version: 1.17.1

Description:
------------
It would be very useful if the main page for each package would include a link back to the pepr/proposal for that package.

This would make it easier for [lead] developers to determine if there is anything useful in the proposal comments and votes that need to be considered/revisited when they are working on the package after it has been accepted.

Some may consider these links as clutter so I think it might be a good idea to have the display of these links configurable from the developers profile page as there is no 'preference' page [as yet].


pearweb: Feature/Change Request 13566 [Open] Check projects/peopls homepage urls with DNSBL
helgith at gmail dot com — 2009-04-29T22:16:42+00:00
pearweb Feature/Change Request
Reported by dufuz
2008-04-02T08:54:41+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
Check all urls inputted against DNSBL and reject them, check in peoples homepage, project homepage and all related url fields


pearweb: Feature/Change Request 13463 [Open] Usability: Make the wiki-ish markup more obvious
daniel dot oconnor at gmail dot com — 2008-03-22T06:49:57+00:00
pearweb Feature/Change Request
Reported by doconnor
2008-03-22T05:58:29+00:00
PHP: 5.2.5 OS:  Package Version: 1.17.1

Description:
------------
I've been around pearweb for a little while now, and I only just discovered the magic trick of typing "bug #1234"

I'd previously tried a number of different tricks, but if I'd had a 'bugtracker wiki markup' how-to link; I'd not have gone uneducated for so long.


pearweb: Feature/Change Request 13151 [Assigned] 'Add Site' feature too restrictive - allow directories
pear at jldupont dot com — 2009-02-03T15:05:15+00:00
pearweb Feature/Change Request
Reported by jldupont
2008-02-19T15:23:39+00:00
PHP: Irrelevant OS: irrelevant Package Version: 

Description:
------------
The 'Add Site' functionality located at http://pear.php.net/channels/  does not permit adding channels of the form 'HTTP://host/directory/' .

" add.php " expects to use only the 'host' part of the URI provided by the user whilst it would require the full URI in order to support the aforementioned case.


pearweb: Feature/Change Request 13075 [Open] reopening "No Feedback" bugs by third party
2008-03-08T15:57:41+00:00
pearweb Feature/Change Request
Reported by ddis11
2008-02-06T16:59:37+00:00
PHP: Irrelevant OS:  Package Version: 1.17.1

Description:
------------
Best explained by example: bug #5257 was suspended last March with status "No Feedback".  While I did not submit this bug, I recently encountered it, and produced a test case as requested by dufuz.  Instead of opening a new bug, I posted the test case and a proposed patch on the bug; however, I have no way to reopen the bug, as I am not the assignee or reporter.

From the bug.php and related source it appears that comments on suspended bugs are still emailed to the assignee, which is nice, but that action isn't as sticky as a bug status change.


pearweb: Feature/Change Request 13048 [Open] Emails with my own comments
till at php dot net — 2008-02-02T15:54:14+00:00
pearweb Feature/Change Request
Reported by till
2008-02-02T15:54:14+00:00
PHP: Irrelevant OS: n/a Package Version: 1.17.1

Description:
------------
When I comment on a bug, I get my comment also via email. I think that is a rather unnecessary message sent out since I know what I just commented.


pearweb: Feature/Change Request 12983 [Open] Be able to delete a user account from the admin panel
arnaud at limbourg dot com — 2008-02-01T15:13:06+00:00
pearweb Feature/Change Request
Reported by arnaud
2008-01-28T01:24:56+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
It would be nice to be able to delete accounts from the admin panel after jumping through the necessary hoops.


pearweb: Feature/Change Request 12891 [Open] Request to add link to MarkMail
jorrit at ncode dot nl — 2008-02-01T19:07:32+00:00
pearweb Feature/Change Request
Reported by jorrit
2008-01-12T06:13:16+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.17.1

Description:
------------
MarkMail (http://markmail.org) has indexed our mailinglist at http://pear.markmail.org/. They ask for a link back. Would that be possible?

I asked them if it were possible to index the PEAR lists, as they already had the PHP lists, and they agreed immediately. It looked to me like an interesting, promising project, so I thought it would be no harm.


pearweb: Bug 12868 [Assigned] Test concering the layout fail
dufuz at php dot net — 2009-06-04T07:05:39+00:00
pearweb Bug
Reported by dufuz
2008-01-09T15:26:49+00:00
PHP: Irrelevant OS: N/A Package Version: CVS

Description:
------------
After the redesign of the page all the tests that test against the layout fail horribly, we have to get them up to standard before the next release.


pearweb: Feature/Change Request 12606 [Open] Package warnings should be free-form text
aharvey at php dot net — 2007-12-04T04:26:30+00:00
pearweb Feature/Change Request
Reported by aharvey
2007-12-04T04:26:30+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 1.16.3

Description:
------------
We should have an option to set the warning message box on package pages (the one that displays messages that a given package is deprecated or unmaintained) to a free-form text string to cope with situations where the current list of options is insufficient. Two examples of this are:

- HTML_QuickForm, which has been superseded by an alpha package, and would be better described by a message pointing users to the new package if they want to live on the bleeding edge.

- DB, where I'd really like to be able to include a message saying that support will cease in August (as discussed on pear-dev a while back) in addition to the deprecation message.

I'm sure there are others. We did discuss this as part of the QuickForm issue on pear-dev about a month ago, but it doesn't look like anyone actually opened a feature request. (If they did, I haven't found it with a search, and I apologise for the dupe.)


pearweb: Feature/Change Request 12520 [Assigned] Reenable comment deleting for certain types of users
dufuz at php dot net — 2008-03-30T15:50:11+00:00
pearweb Feature/Change Request
Reported by dufuz
2007-11-24T18:38:27+00:00
PHP: Irrelevant OS: NA Package Version: 1.16.3

Description:
------------
At the moment we have all the functionality to delete comments, the site possessed that ability in the past since it's a fork from bugsweb but for some reason it was taken out and now I want to reinstate that because of spam people have been getting.

At the moment only pear.bugs.admin can do it but that's a bit much, I think I might want to allow pear.dev people in general to delete comments even if it's not their own packages.


pearweb: Feature/Change Request 11596 [Open] Site should have a place to post jobs.
pear at joestump dot net — 2008-05-11T09:07:56+00:00
pearweb Feature/Change Request
Reported by jstump
2007-07-12T17:57:25+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
The website should have a place to post jobs. Ideally, there'd be a pear-jobs@lists.php.net mailing list (or jobs@lists.php.net when PHP.net creates its own) as well so people could subscribe to job notices.


pearweb: Feature/Change Request 11368 [Assigned] Inform package authors about new notes
wiesemann at php dot net — 2008-01-23T14:29:56+00:00
pearweb Feature/Change Request
Reported by wiesemann
2007-06-19T11:15:56+00:00
PHP: Irrelevant OS: Irrelevant Package Version: CVS

Description:
------------
Everytime a note is added to a page in the manual that belongs to a page, the maintainers of that package should get an email. They could then transform it into a doc bug (once this feature is finally ready ...), approve or delete it, or comment on it.


pearweb: Feature/Change Request 11319 [Assigned] allow time range selection for download stats
cweiske at php dot net — 2008-02-06T17:44:11+00:00
pearweb Feature/Change Request
Reported by cweiske
2007-06-14T15:20:41+00:00
PHP: Irrelevant OS:  Package Version: 1.16.0

Description:
------------
It would be helpful if the package download stats page would allow selecting the timeframe for download counts.

Old packages normally have higher download numbers than new ones, so it is interesting to see which packages have been downloaded most in the last month.


I think it'd be enough to give a hard number of choices:
1 day, 1 week, 1 month, 2 months, 3 months, 6 months, 1 year, 2 years, all time


http://pear.php.net/package-stats.php


pearweb: Feature/Change Request 11304 [Open] The manual should show a "deprecated" warning when the package is
arnaud at limbourg dot com — 2008-01-26T22:46:12+00:00
pearweb Feature/Change Request
Reported by arnaud
2007-06-13T02:23:10+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
When a package is marked as deprecated the corresponding section in the manual should show this.


pearweb: Feature/Change Request 11271 [Open] unit tests for packages.php
greg at chiaraquartet dot net — 2008-02-05T12:05:32+00:00
pearweb Feature/Change Request
Reported by cellog
2007-06-10T23:50:09+00:00
PHP: 5.2.2 OS:  Package Version: 

Description:
------------
packages.php needs unit tests


pearweb: Feature/Change Request 11222 [Assigned] The U of the Western Cape and the FSIU want to be African mirror
greg at chiaraquartet dot net — 2008-01-12T10:08:29+00:00
pearweb Feature/Change Request
Reported by cellog
2007-06-04T14:33:59+00:00
PHP: 5.2.2 OS:  Package Version: 1.16.0

Description:
------------
The University of the Western Cape and the FSIU (Free Software
Innovation Unit) would be glad to do an African Mirror according to Paul Scott.


pearweb: Feature/Change Request 11219 [Assigned] Cleaning out inactive PEPr proposals
mj at php dot net — 2008-04-15T07:45:23+00:00
pearweb Feature/Change Request
Reported by mj
2007-06-04T05:01:58+00:00
PHP: Irrelevant OS:  Package Version: CVS

Description:
------------
As decided by the PEAR Group in yesterdays meeting, PEPr proposals that have been inactive for more than three months will trigger warnings sent to the proposer.  If proposals are inactive for more than six months, they will be deleted.


pearweb: Feature/Change Request 11218 [Open] Give  unmaintained packages more visiblity
arnaud at limbourg dot com — 2008-04-20T10:56:37+00:00
pearweb Feature/Change Request
Reported by arnaud
2007-06-04T02:15:47+00:00
PHP: Irrelevant OS:  Package Version: 

Description:
------------
Currently the list of unmaintained packages is hard to find and has restriction access in place (pear.dev karma).

The list should more visible (and generated regularly as generating it live takes up some resources).


pearweb: Feature/Change Request 11044 [Open] Better suggestions for similar bugs/requests
wiesemann at php dot net — 2007-11-18T08:30:33+00:00
pearweb Feature/Change Request
Reported by wiesemann
2007-05-15T07:50:32+00:00
PHP: 5.2.1 OS:  Package Version: 1.15.2

Description:
------------
The bug tracker suggests possibly similar bugs after submitting the form. The current implementation also shows bugs for e.g. Auth if I report something for e.g. HTML_Table. Even if an error is the same in both packages (e.g. a PHP notice caused by the same coding style), it is very unlikely that one of the bugs should not be reported.

To keep it short: The way the suggestions are generated should be revised. The suggestions could even be restricted to the package, the package and its subpackage (maybe hard to implement, but interesting for e.g. Structures_DataGrid or Validate), or at least to categories.

(To give a real-life example: While submitting this request, a got three hints on pearweb, but also two hints on HTTP_WebDAV_Server and HTTP_Request.)


pearweb: Feature/Change Request 11026 [Assigned] Reminder for pear-group about accounts not being processed
dufuz at php dot net — 2008-02-09T14:03:27+00:00
pearweb Feature/Change Request
Reported by dufuz
2007-05-13T13:41:23+00:00
PHP: Irrelevant OS:  Package Version: 1.15.2

Description:
------------
The idea is to have a cronjob run X many times a week (perhaps only once) and check if there are any accounts or karma requests that haven't been processed, we'd define a stalled age, probably a week and if the request is 1 week or more then pear-group would be emailed about it and thus someone could jump in and resolve it.

This way pear-group doesn't have to assign a certain person to monitor the account approving stage and also if people forget it then we will have these reminders to bug us.


pearweb: Feature/Change Request 10955 [Open] pearweb installation script should remember your alternative DSN
daniel dot oconnor at gmail dot com — 2008-02-01T15:46:33+00:00
pearweb Feature/Change Request
Reported by doconnor
2007-05-06T06:21:37+00:00
PHP: 5.2.1 OS:  Package Version: 1.15.0

Description:
------------
When you first install pearweb, you (sometimes) go through the fooling about of pointing to an alternative DSN.

After you've done that, you get connection failures when you visit the installation in your browser.

the run-script should:
 1. prompt me for my DSN
 2. if it's different to the default, write it out to file (pear-local-configuration.php) along with any other configuration (PEAR_TMPDIR; for instance; on windows systems)
 3. alter the httpd.conf to include your defaults as well
 php_value auto_prepend_file pear-local-configuration.php


pearweb: Feature/Change Request 10951 [Assigned] PEPr Activity Feed
mj at php dot net — 2009-05-08T07:05:01+00:00
pearweb Feature/Change Request
Reported by mj
2007-05-06T05:22:24+00:00
PHP: Irrelevant OS: Irrelevant Package Version: 

Description:
------------
I'm writing this down here so that I do not forget about it until I find time to implement it later:

We need a PEPr activity feed for individual proposals, which includes

* changes by the proposer
* comments
* votes
* status changes

This way people (including the proposer) being interested in a proposal can easily keep track of the progress.


pearweb: Feature/Change Request 10860 [Assigned] Roadmap Col on Bug Tracker View
demon dot gene at gmail dot com — 2007-11-18T08:30:59+00:00
pearweb Feature/Change Request
Reported by ashnazg
2007-04-27T08:51:47+00:00
PHP: 5.1.6 OS: irrelevant Package Version: 1.14.0

Description:
------------
Could a "Roadmap" column be added to the already tight Bug Tracker view?  It would help see at-a-glance which bugs were unassigned to maps, even if it showed only a boolean flag rather than the map number.  Perhaps the "Summary" column could squeeze in a little to make room, since it already wraps longs lines in its rows.


pearweb: Feature/Change Request 10469 [Assigned] ability to edit user notes to correct errors/improve things
greg at chiaraquartet dot net — 2008-01-23T13:37:04+00:00
pearweb Feature/Change Request
Reported by cellog
2007-03-23T09:36:46+00:00
PHP: Irrelevant OS: n/a Package Version: 1.11.0

Description:
------------
People sometimes submit very nice notes that could be tweaked to be even better, it would be nice to be able to edit the note directly on the doc page