possible problem with Newsletter signup


Am I doing something wrong here?
Thanks in advance for your help!


If you don't want a user to see a block, you need to use the if_in_group Comcode tag.
Like…
Code
[if_in_group="*,!1"]
[block]main_newsletter_signup[/block]
[/if_in_group]
This allows everybody in a group except group #1 (Guests) to view the block.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.


Excellent. Thanks Chris.Chris Graham said
You disabled access to the newsletter page, but the block doesn't use the page.
If you don't want a user to see a block, you need to use the if_in_group Comcode tag.
Like…
This allows everybody in a group except group #1 (Guests) to view the block.Code
[if_in_group="*,!1"]
[block]main_newsletter_signup[/block]
[/if_in_group]
From “Post #6,709”, 14th May 2020, 6:32 pm
I would like to mention that I did sort of try this, but I used the following code to do so:
Code
{+START,IF,{$NOT,{$IS_GUEST}}}
[block]main_newsletter_signup[/block]
{+END}

Just wanted to share that information with you, in case you wanted to look into it further (or maybe I did something wrong).
Edit: Never mind

Last edit: by cwdean


Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.


Chris Graham said
Possibly it's because you have two panel_left's (one for welcome zone, one for site zone), as discussed in your other topic.
From “Post #6,712”, 14th May 2020, 7:12 pm
Sorry Chris. I think I was editing my previous post while you were responding

But on a side question, I notice the following in the editor:

This is probably a VERY stupid question, but how do I edit the tempcode in this case? I see Tempcode tag but can't figure out how to edit it.


You need to go into the editor's source view and edit it in XML form.
Or, turn off WYSIWYG.
Become a fan of Composr on Facebook or add me as a friend. Add me on on Mastodon. Follow me on Minds (where I am most active). Support me on Patreon
- If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
- If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
- If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
- If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.