-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
All,
I'm wondering if you've given any thoughts on this feature. Is it
desirable to have it? Would the described scenario be a good solution
for it? Any further comments on the PR itself?
Thanks,
Juca.
On 01/24/2014 11:37 AM, Juraci Paixão Kröhling wrote:
A little bit of background on this one: this came up as a bug
report, as a not marked as "visible" (checkbox "Visible" on the UI)
doesn't shows up on the navigation, which effectively makes the
node "hidden". But an user that knows the URL of said node would
still be able to see it and share the URL with other users.
I understand that "fixing" this bug would introduce a change in
the behavior, which might affect people using this as a feature. As
in: do not mark this node as visible, but put a link to it from
inside the content of a page. If we suddenly just restrict access
to this page, this behavior would be broken.
The idea then was to ask the user explicitly if access to the node
should be restricted. For all existing nodes, it defaults to "no".
For new nodes, if the publishing date is set, this field is checked
by default.
Does it makes sense?
Juca.
On 01/24/2014 11:32 AM, Bolesław Dawidowicz wrote:
> W dniu 23/01/14 17:00, Juraci Paixão Kröhling pisze:
>>
>> @Julien: do you want to discuss whether this feature would be
>> accepted into master? Should I send a PR, or would you prefer
>> to review it on my repository?
>>
> Btw :)
_______________________________________________ gatein-dev mailing
list gatein-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/gatein-dev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iQEcBAEBCgAGBQJS5lmEAAoJECKM1e+fkPrXJsIIAImBqb95CnoR8mLpYIAvI+zc
gIrrlZXYKeui8955MHQVC2dfaE9272Ltdj7Apqtlm4tvOm5W8YVLOd0vXGfaxyFH
k3+3F2+a2dPnVd7wmG8s6eFssD/uc7Ko6Mb3hxWpV1LHAj32mNSqMc2twDVWzZCn
nSxPxLbkfOQhu8I4c8DJWOy5Uq4XPWCnhtq4qCorS3A6kYb2/kNIq3oBQ0Ess/Nk
2295DAEMeYBhJJWw3k87DRZ9DLsjjJ66ej82s9e4z7v0p4hbBl83hZLiwaB8nOM0
K3KAWnDVThcVZr43llt8q8GhBRk5twKcpDCYQ+8k+gFm5uOa1EmoIvJRQQ6DkJY=
=48uM
-----END PGP SIGNATURE-----