[MAGNOLIA-2660] Adding new MIMEMappings (xpi) Created: 11/Mar/09 Updated: 01/Nov/10 Resolved: 18/Mar/09 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.6.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor |
| Reporter: | Jurjen de Groot | Assignee: | Zdenek Skodik |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | MIMEMapping, xpi | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Template: |
|
||||
| Acceptance criteria: |
Empty
|
||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||
| Date of First Response: | |||||
| Description |
|
How can we add a new MIMEMapping so we can serve .xpi files? we assumed that we could add a new MIMEMapping in the config tree named xpi with a node data named extension with the value xpi and a node data named mime-type with the value application/x-xpinstall. This doesn't seem to work like that. So, is it possible to add new MIMEMappings ourselves? And if so, what do we seem to be missing? |
| Comments |
| Comment by Magnolia International [ 11/Mar/09 ] |
|
Hi, This Jira project is used to report bugs and improvements on the current codebase. What you're describing seems to be appropriate, we'd need to see the actual data you entered to be sure. New mappings should be picked up automatically. Also, we'd need to understand what doesn't work; what was expected and what happened instead. For such questions or issues, please use either the mailing lists or your dedicated support channel if you have a support contract with us. If so, you can directly Move this issue under the Support - Magnolia project. The reason we can't do it ourselves is so to avoid having to guess details about your setup. Your attention to detail will be appreciated. If this ends up being an actual bug in Magnolia (or something that can be improved), Cheers, -greg |
| Comment by Zdenek Skodik [ 18/Mar/09 ] |
|
this issue has been moved to [SUPPORT-256] |
| Comment by Magnolia International [ 18/Mar/09 ] |
|
reopening just to set the "resolution" properly. |
| Comment by Magnolia International [ 18/Mar/09 ] |
|
Zdenek: setting the proper resolution field is important - in this case for instance, the issue was not "fixed". |
| Comment by Zdenek Skodik [ 01/Nov/10 ] |
|
To get this working (trigger the installer immediately) one needs to allow inline editing (by xpi mime type or by path) of DMS content as documented. |