[MGNLPN-193] Add possibility to disable adding of cookies Created: 06/Nov/14 Updated: 07/Nov/14 Resolved: 07/Nov/14 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | 1.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Prabhakar Sekar | Assignee: | Unassigned |
| Resolution: | Workaround exists | 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
We should:
Moreover BeanCookie, CookiesFormProcessor could be moved to Form module since are not personalization specific. Original issue: As of now, we could not use the application as the application needs our cookies to work properly. Please check and get back. Do let us know if you have any workaround for this problem. |
| Comments |
| Comment by Roman Kovařík [ 06/Nov/14 ] |
|
Hello, I suppose that you want to be able to use personalisation features so disabling of this filter is not an option for you, right?
B] Or you can implement your own visitor detector filter by extending of the default one to meet your needs. (info.magnolia.personalization.visitor.VisitorDetectorFilter). Hope that helps. |
| Comment by Prabhakar Sekar [ 06/Nov/14 ] |
|
Hi, Thanks for the reply. Please let me know how i can disable this filter. Since the application itself is not working properly, we can disable the filter temporarily.Also, Please help me by sharing the link to the documentation on this Filter so that we can understand it and try to use it in a better way. |
| Comment by Prabhakar Sekar [ 06/Nov/14 ] |
|
Hi, We set the level as suggested and now it seems to be working fine. Thanks again. |
| Comment by Roman Kovařík [ 06/Nov/14 ] |
|
Hi, I'm glad that this workaround works for you. Here you can read more about personalisation. Regards. |