forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From iss...@cocoondev.org
Subject [JIRA] Commented: (FOR-450) Input plugins broken
Date Sat, 02 Apr 2005 19:11:18 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Sat, 2 Apr 2005 1:10 PM
       Body:
Arrrggghhhh!!!

I'd missed the fact that some new i18n stuff had been inserted *before* the plugin match.

The plugin match *must* go before any core matches that deal with *.xml (as you have now done).

You are correct that it is only affecting the plugins using sourcetype because all other plugins
are matching on something other than *.xml

I've looked at your change and it looks good. I'll do more rigorous testing before closing
this issue though.

Can someone test the i18n functionality with this new mount position.

(thanks for finding this it was driving me up the wall!)
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-450?page=comments#action_12198

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-450

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: FOR-450
    Summary: Input plugins broken
       Type: Bug

     Status: Unassigned
   Priority: Blocker

    Project: Forrest
 Components: 
             Plugins (general issues)
   Fix Fors:
             0.7-dev
   Versions:
             0.7-dev

   Assignee: 
   Reporter: Ross Gardler

    Created: Mon, 28 Feb 2005 4:34 PM
    Updated: Sat, 2 Apr 2005 1:10 PM

Description:
Input plugins are not working in Head. Unfortunately I do not have the time to find the cause
right now. What I can say is that r153977 works fine.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message