opt-out | Opt out fees automatically for McGill students | Frontend Utils library

Your organisation is using a "Site" or "Experience Cloud" (formerly known as Customer / Partner Community, formerly known as Customer / Partner Portal). Go to Setup -> Sites or Setup -> Experience... and have a look.

If you had no idea you're using a community there's a chance you don't have real community users & licences (cheaper than regular licenses but still), you might have just the "guest user" for unauthenticated access. Be careful what you expose to guest users

There might be some trailheads and videos if you're lost.

1. Go to community builder and create new page for your component (but don't add the component yet, maybe add just some plain text). The page editor is similar but not identical to "Lightning App Builder" editor. This is the part where you choose "self", "opt-out" etc.
2. Maybe add your page to Navigation Menu at top of the page.
3. Hit "Publish" and check if you can see the new page.
4. Compare your component's "meta.xml" file with the other two. You'll need to add a target (probably lightningCommunity__Page) to it to indicate it's OK to drop it on community page. Deploy.
5. If your component uses Apex - you need to grant permission to run this class to the guest user (or normal community users, if it turns out you actually have them). Guest user is still a Profile, you have all the normal checkboxes - but it's bit hidden. Steps depend whether you have a Site or community.
6. You're ready to go back to your page, drop your component on it and hit Publish again.
7. If you think there are apex errors - debugging guest users is bit of a pain too. Go to Setup -> Debug logs and search users with "guest" in name. Something like "{your community name} Site Guest User" should pop up.

There are 2 ways to fix this problem.

1. It seems that you are importing modules to some js files but not using them so avoid using unnecessary imports and only import a module when you are using it on the page. If you are not using it then avoid importing that module to the js file.

1. Install the following module npm install --save-dev eslint-plugin-react. (for developers using NPM) or yarn add --dev eslint-plugin-react. (for developers using Yarn)

   Then, in your .eslintrc.json, under extends, include the following plugin:

You can achieve this using the exception_handler gem - https://github.com/richpeck/exception_handler

If you do not want to add another dependancy, here is a tutorial on how you can build it yourself - https://medium.com/ruby-on-rails-web-application-development/custom-400-500-error-pages-in-ruby-on-rails-exception-handler-3a04975e4677

you can add the paths to the admin files in the setup here

I guess you have used the same approach to configure languages Kontent gatsby source plugin as it is in starters.

According to the error, I would guess your environment variables are not propagated to Cloudflare. So process.env.KONTENT_LANGUAGE_CODENAMES is undefined -> which causess the error cannot read properties of undefined (reading 'split') on gatsby-config.js:30:67.

Check if HEROKU_API_KEY is correct and that heroku_app_name is unique. Also this line seems sketcy: Detected both "build" and "heroku-postbuild" scripts Running heroku-postbuild. Maybe refactor heroku-postbuild in build and run only build.

views.py:

You can add .verticalScroll(rememberScrollState()) modifier to your content to make it scrollable.

According to this post, .NET Core 3.1 added an environment variable called DOTNET_NOLOGO, which, when set (to 1? to anything?) will suppress the welcome message.

This, much more recent post confirms it's still relevant.

Can you add this env variable to your CI pipeline environment?