[MAGNOLIA-429] Allow publishing from a public instance Created: 09/Jun/05 Updated: 15/Jun/05 Resolved: 10/Jun/05 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | admininterface |
| Affects Version/s: | 2.1 Final |
| Fix Version/s: | 2.1 Final |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Fabrizio Giustina | Assignee: | Fabrizio Giustina |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: |
| Description |
|
Actually activation is enabled only in admin instances: in some scenarios could be useful to allow activation from a public instance too. For example you can have an admin instance, a public test instance, and a production instance. (of course enabling publishing from a public instance should be optional) |
| Comments |
| Comment by Fabrizio Giustina [ 09/Jun/05 ] |
|
in svn: now in the server configuration, near to "admin", there is another flag called "publisher" which can be used to enable activation in a public instance. |
| Comment by Boris Kraft [ 10/Jun/05 ] |
|
Fabrizio, what do you think about simply enabling activation if active subscribers exist? Then there is no need for yet another flag.
|
| Comment by Fabrizio Giustina [ 10/Jun/05 ] |
|
ok, I simply added the "publisher" flag to avoid changing the behaviour of existing configurations (if you don't add this new configuration value everything works as before), but I agree that simply checking available subscriber would be better. (reopening issue) |
| Comment by Fabrizio Giustina [ 10/Jun/05 ] |
|
changes in svn. |