Page 1 of 1

Privacy: Create Request

Posted: Thu Nov 01, 2018 5:04 pm
by JAVesey
Evening all,

I have a quick query which I'm sure someone will by able to answer about using one of the privacy tools in v3.9.0

What I've done:
1. The "Privacy - Create Request" form can only be seen by logged in users - default behaviour and as I want it.
2. I've made the required menu item (Privacy --> Create Request) and it's "green lighted" on the dashboard.
3. I've made the menu item "public" so anyone can see/access it.

So far so good, but here's the bit I need help with...

I have:
1. User clicks on the link and goes to the login form.
2. After logging in, the user is taken to their profile.
3. User has to click on the menu item again to get to the "Create Request" form.

I want:
1. User clicks on the link and goes to the login form.
2. After logging in, the user is taken directly to the "Create Request" form.

What do I need to do/change to get what I want rather than what I have?

TIA

Re: Privacy: Create Request

Posted: Sat Nov 03, 2018 7:53 am
by darb
+ 1

Re: Privacy: Create Request

Posted: Sat Nov 03, 2018 11:16 am
by SharkyKZ

Re: Privacy: Create Request

Posted: Sat Nov 03, 2018 11:43 am
by JAVesey
SharkyKZ wrote:
Sat Nov 03, 2018 11:16 am
Test this please https://github.com/joomla/joomla-cms/pull/22927.
Tested and happy to confirm that it works beautifully :)

Thank you.

Re: Privacy: Create Request

Posted: Sun Nov 04, 2018 2:06 pm
by wfnitsup
I find the fact that the user must first login as good but there is no indication that the user must then click the menu item a second time to get the form.

This only gives a selection of Export or remove/delete. I believe a explenation of what the user may do here. And a text field needs to be added so the user can add text if requied.

Therefore the menu Item need only appear once the user has logged in. For me this was not clear in the first instance.

To create a request is good but the user needs to be informed how this works and what they can do and how they can do it without keeping it a secret as the case seems to be.

we must remember not everyone is a IT engineer.

Look foreward to any constructive responses.

Re: Privacy: Create Request

Posted: Sun Nov 04, 2018 2:27 pm
by JAVesey
wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
I find the fact that the user must first login as good but there is no indication that the user must then click the menu item a second time to get the form.
This was the reason for my initial query.

wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
This only gives a selection of Export or remove/delete. I believe a explenation of what the user may do here. And a text field needs to be added so the user can add text if requied.
Of course, and that is up to the site owner/maintainer to do by whatever means they consider appropriate. There are lots of ways to achieve this.

wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
Therefore the menu Item need only appear once the user has logged in. For me this was not clear in the first instance.
I don't personally agree; I wanted the menu item visible publicly -->login-->redirect to form.

This is what the amended file on Github achieves.

wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
To create a request is good but the user needs to be informed how this works and what they can do and how they can do it without keeping it a secret as the case seems to be.
I would have thought that this would be in a site's privacy policy/notice and a link to it from the form page (see above on adding text) would be a good idea.

wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
we must remember not everyone is a IT engineer.
Agreed, but if you're running a site then a small amendment to one file shouldn't be beyond most people. Hopefully this one small amendment will be reflected in a future core update for those who don't want to amend/edit a core file (I can understand why!).

wfnitsup wrote:
Sun Nov 04, 2018 2:06 pm
Look foreward to any constructive responses.
Hopefully you'll see this as such ;)

Re: Privacy: Create Request

Posted: Sun Nov 04, 2018 5:14 pm
by wfnitsup
Thank you for your swift reply.

I must admit that I am not a code expert and try to keep my fingers out of the gearbox.

Ajusting "some" css, ini and php" files is places that are easier to understand what happens. Like the footer area of a template, or the colours, and even text to fit the local requirement.(Germany).

But I don't try too much and do this offline in a local and safe environment (XAMPP).

This is why I miss getting more information about how to do things when I update or add a component. I have to do a lot of trial and error to find out how someting ticks.

I know that documentation is available but this dosen't always have the information I require to go forward, as though it has been written for experts only.

The Privacy Policy for Germany does not explain how to use an online form. I would have expected this to be part of the Privacy component, or at least have a way in which the Administrator can easily add one and not have to delve into code that they don't understand. As in my case.