Nathan Explosion

Don't need to go near the database - go to the post that is the real first post, and edit it. You can set the publish date back to a prior date, and save the edit.

Did you tick the indicated box when downloading?

Try clicking it - you go to the post from which the quote was taken.

Which would be a bug if it was showing, as you can only see resources that are compatible with the version you are running.
The more correct answer would be related to the fact you are in the Members group on here, and not Clients... which would be an indication that your license has expired. If you have just renewed then you need to logout and back in to trigger the group movement to occur.
And an even more correct answer is that the resource is not available for purchase, as the vendor is also not in the Clients group.

If you ever want to test later versions of Chrome safely, install Chrome Beta (which is the 'Next' version) and Chrome Dev (which is the next beta) from the Google Play store. 3 separate browsers, thrice the fun!
 

Yes - it's a moderation permission. If they can't use it currently then you have likely set up restrictions - the below is on the 'Content' tab:

Toggle this one off:

Result:

System -> (Support) Get Support -> Clear System Caches

Take a look at this, in that case:
 

And if you are self-hosted, you would then delete the /applications/downloads folder (I am assuming that the folder is called 'downloads') from your installation.

When creating a page, select the 'Manual HTML' option and then deselect 'Use suite HTML wrapper' in the resulting configuration - it can't be done with the Page Builder, as far as I am aware (although probably could be achieved if you want to begin hiding things using CSS)

Got to achievements settings, click the rebuild button.

If a user has access to more than one theme then they see the theme selector - so if you don't want the theme selector seen, modify permissions on themes theme to not make them available to groups.

Importing uses an upload of a CSV file to populate the member list, so if you can create the source file then go for it - but it wouldn't be associated with AD.
However, you could always look at implementing the LDAP login method and allow your users to register using their AD credentials. If it's Azure AD, or your on-premise AD is sync'ed to Azure AD, then you could use the Microsoft login method instead.
 

Microsoft no longer allow a 'Never' expiry - 2 years is the limit (so that's an update for the document)
Value (it states that in step 7 of the guide) - has to be grabbed at the time of creation, as it is obscured from view on later views. If you didn't grab it then just delete the existing one and create a new one.
And the final tip...put a reminder into your calendar for a few days prior to the expiry date, to remind you to create a new value.

Samsung?
 

Take a look at \IPS\Login::usernameIsInUse (system\login\login.php)

app = core
location = global
group = global
{template="memberBaddge" app="core" location="global" group="global" params="$comment->author()"} If you had it in core -> front -> global then your code would be fine as postContainer is in front too.
 

0 = false
1 = true

Step 1 - create a group
Step 2 - give that group moderator permissions
Have you now done both?

I don't think you've noticed that the provided atachment link is missing the &key parameter which, if missing, means that the attachment won't be accessible even if it was there because a security check fails as a result - and will present the following message:

 
If it was me investigating this, I would be looking at the content that contains the attachment link, to determine if it is missing the key element there. If so then it was possibly posted in a version when the &key= element wasn't being added to attachment links due to an IPS bug that has since been resolved...but hey, that's me.
 
 

Right click the item and inspect the item before you click it and then after you click it, then find the classes that are applied to it before/after:
BEFORE

AFTER

From the dev tools css files - the color isn't changing, the opacity is:
.cToken.cToken_selected { opacity: 0.7; } So override it...
.cToken.cToken_selected { opacity: 1 !important; } This kind of stuff is usually a lot easier for others to figure out if you post a link to a site (which allows people to look at the html/css) instead of a screenshot (which only allows people to look at a pretty picture)