Changing Board access Message to guests

[frootloop]

Forum URL: thewoodsforum.boards.net/

Is there a way to change the message a guest receives when they click on a thread enabled to members & staff only? 

Currently, this is the message a guest (or member) would receive if they aren't logged on:
"Oops, there was an error"
"You do not have permission to access this board"

(Screenshot of the current message)


This message certainly won't encourage guests to become a member; it seems harsh, and uninviting. It doesn't explain that they simply need to either log on or create a free account to see the board.

If guests are new to Proboards they would have no clue as to why they are blocked, or what the criteria would be to access the board.

I'd like it to say:

Oops, there was an error 

Access to this board is only available to forum members. Please log in, or create an account for full access to all threads.


PS: Why doesn't Grammarly work on Proboards?  (it only works on the shoutbox, not on posts or PMs)

[Scott]

frootloop -

Give this a try. Add this script to the Global Header
(Admin > Structure > Headers & Footers > Global Header & Footer > Header)

<script type="text/javascript">
$(document).ready(function(){
if(/\/board\//i.test(location.href) && $('.container.error').length && !pb.data('user').is_logged_in)
$('.container.error > .content').html('Access to this board is only available to forum members. Please log in, or create an account for full access to all threads.');
});
</script>

[atlantic]

Apr 15, 2024 14:28:43 GMT -8 frootloop said:

Forum URL: thewoodsforum.boards.net/

Is there a way to change the message a guest receives when they click on a thread enabled to members & staff only? 

Currently, this is the message a guest (or member) would receive if they aren't logged on:
"Oops, there was an error"
"You do not have permission to access this board"

(Screenshot of the current message)


This message certainly won't encourage guests to become a member; it seems harsh, and uninviting. It doesn't explain that they simply need to either log on or create a free account to see the board.

If guests are new to Proboards they would have no clue as to why they are blocked, or what the criteria would be to access the board.

I'd like it to say:

Oops, there was an error 

Access to this board is only available to forum members. Please log in, or create an account for full access to all threads.


PS: Why doesn't Grammarly work on Proboards?  (it only works on the shoutbox, not on posts or PMs)

Sometimes boards are only available to specific forum members. Just saying.

[Scott]

Apr 15, 2024 15:15:50 GMT -8 atlantic said:

Sometimes boards are only available to specific forum members. Just saying.

Sorry, not following?

[atlantic]

Apr 15, 2024 15:23:05 GMT -8 Scott said:

Apr 15, 2024 15:15:50 GMT -8 atlantic said:

Sometimes boards are only available to specific forum members. Just saying.

Sorry, not following?

If a board's permissions are set to allow (or exclude) specific members - say those in a particular member group or rank - members that don't have access to that board will get that message despite being members of the forum.

[Chris]

Apr 15, 2024 15:45:13 GMT -8 atlantic said:

Apr 15, 2024 15:23:05 GMT -8 Scott said:

Sorry, not following?

If a board's permissions are set to allow (or exclude) specific members - say those in a particular member group or rank - members that don't have access to that board will get that message despite being members of the forum.

The code in this post allows catering the message to guests, specific groups,^* or users.
The code was subsequently encapsulated into a plugin later in the thread and finally added to the support plugin board library.

[frootloop]

Apr 15, 2024 14:33:31 GMT -8 Scott said:

frootloop -

Give this a try. Add this script to the Global Header
(Admin > Structure > Headers & Footers > Global Header & Footer > Header)

<script type="text/javascript">
$(document).ready(function(){
if(/\/board\//i.test(location.href) && $('.container.error').length && !pb.data('user').is_logged_in)
$('.container.error > .content').html('Access to this board is only available to forum members. Please log in, or create an account for full access to all threads.');
});
</script>

Thanks so much! 

[frootloop]

Scott

This is perfect and exactly what I wanted!

I just wanted to thank you for not only the CSS but for guiding me to the exact placement; couldn't have been any easier.

Do you happen to know why the Grammarly extension doesn't work on posts or PM but works on the shoutbox? (It is set to "allow" Grammarly on the site (thewoodsforum.boards.net) and it works on all other sites, with the exception of any Proboards)

[bigballofyarn]

Apr 16, 2024 4:42:45 GMT -8 frootloop said:

Do you happen to know why the Grammarly extension doesn't work on posts or PM but works on the shoutbox? (It is set to "allow" Grammarly on the site (thewoodsforum.boards.net) and it works on all other sites, with the exception of any Proboards)

I installed Grammarly to test this for you. It works for me as a guest within posts on your forum. Are you the only one experiencing an issue in posts? Obviously, I can't test PMs as a guest.

[frootloop]

Apr 16, 2024 4:51:27 GMT -8 bigballofyarn said:

Apr 16, 2024 4:42:45 GMT -8 frootloop said:

Do you happen to know why the Grammarly extension doesn't work on posts or PM but works on the shoutbox? (It is set to "allow" Grammarly on the site (thewoodsforum.boards.net) and it works on all other sites, with the exception of any Proboards)

I installed Grammarly to test this for you. It works for me as a guest within posts on your forum. Are you the only one experiencing an issue in posts? Obviously, I can't test PMs as a guest.

I have just gone through a ton of "fixes" such as removing app & reinstalling, clearing caches, turning off all other extensions.

Now I get the Grammarly extension to work on the Quick Reply & shoutbox but it still doesn't work on the Reply posts and PMs.

I'm using Chrome but I tried Firefox, Edge, and even an AOl browser with the same results.

It has to be a setting or other program blocking it but I'm at a loss as to what I should do next

[bigballofyarn]

I wonder if it's partly Grammarly itself. I can't say that with any certainty as it's only been installed for about an hour. I let it stay enabled while browsing around and did notice though that it didn't recognize certain text fields as text fields despite my ability to enter text. I know this doesn't exactly help, but it potentially sheds light on how Grammarly operates and how it may be appearing differently for everyone.

[Chris]

Feb 26, 2022 7:53:53 GMT -8 Grammar Queen said:

Feb 23, 2022 5:34:42 GMT -8 📚 Dianne 📚 said:

Does anyone have any idea why my Grammarly wouldn't be working in here?


I checked it out elsewhere, and it seems to be working okay.

SPOILER: Click to show

Grammarly Support said:

I do not see the G icon on a certain web page or in a certain text field but see it on other web-pages.

There are a few reasons the Grammarly browser extension may not work on a web page: 

• The page may not be supported by the extension.
• The text box is incompatible with Grammarly.
• The text box was built using iFrame.
• The text box may have incompatible dimensions.
• Website owners might have deactivated Grammarly on their web page.

Sept 19, 2021 1:35:58 GMT -8 Stealth said:

Grammarly would need to code an exception for the Proboards platform in order to get it working on PREVIEW since that side of the editor is built with an iframe .

Sept 17, 2021 5:57:09 GMT -8 Stealth said:

The proprietary Proboards WYSIWYG is built client-side so if you wish to modify it then you should first listen for the jquery-ui custom event wysiwygcreate then do your mods when it is ready to be modified:

$(document).on('wysiwygcreate',function(event){
document.querySelector('div.visual-editor > iframe')...
})


ETA: Incidentally if you're from the Grammarly Development team that is the approach you need to take to get your extension working on Proboards' preview tab. The iframe is SAMEORIGIN so accessing content is not an issue.

Sept 10, 2021 19:32:27 GMT -8 Stealth said:

You may also want to try the following in case the browser (not the plugin itself) is the entity responsible for placing restrictions on the installed plugin causing it to display the message: "Grammarly is active, but key features are missing"

Grammarly Features Error

Feb 27, 2022 9:43:24 GMT -8 Kami said:

Feb 27, 2022 5:32:34 GMT -8 📚 Dianne 📚 said:

Okay, thank you, everyone, but you are all getting a little too (okay, a lot) technical for me. Right this moment, I see the Grammarly icon, so I'm good.

TLDR: based on grammarly's FAQ, any writing space built with an iframe (which is what PB v5 uses for the preview editor) doesn't display the grammarly icon. Switching over to the BB Code editor will allow the grammarly icon to appear because it is not built with an iframe.

In order to change this for the preview editor, Grammarly would need to add something on their end.

[Chris]

Apr 16, 2024 6:37:58 GMT -8 bigballofyarn said:

it didn't recognize certain text fields as text fields despite my ability to enter text.

Grammarly doesn't analyze text in fields that are marked as sensitive, such as password and credit card fields. It is also blocked from analyzing text in search fields, URL fields, and email address fields. This is why you will not see Grammarly appear when you use the Google search field.



There could also be technical reasons why Grammarly does not appear. For example, if the text field is too small (min: 301x28) or if it was built using an iFrame. In some cases, it's also possible that Grammarly has been blocked by the website owners.

Read More...