Nathan Explosion

What version are you currently on?

A suggestion..I recently wasted 30 minutes of my time looking into a similar issue on my site. Couldn't reproduce. The report from the user was 'The site doesn't allow me to edit the post' - the actual issue was 'i don't know where the edit option is'

From the time the content item was submitted.

A quick search for nginx gives this as the first hit...

Then you move your installation from root to /forums/ and enable friendly urls and rewrites so that index.php isn't included in the URLs (search your ACP)

In that case then just do this bit and forget about the /forums bit then. Then you have: domain.com/index.html and domain.com/index.php

In that case, index.php is already your landing page and that will open /forums/* for Forums pages. If you want to use a static HTML page then create index.html....and set your hosting to open that as your default page (so instead of .php file, .html file)

Do you have Pages? What do you currently have set as your default application in the ACP?

I know you did - but as they didn't mention that explicitly, I just wanted to point out what I did. You are now asking the right questions...if the suite is installed in /forums/ then it would need to be moved to the site root, and then the fun begins.

Might not be true, actually - they may have the suite installed at site root, with Pages set as the default application (with its associated default page being the landing page)...."Forums" would then be site.root/forums Example (this very site) Pages: https://invisioncommunity.com/ Forums: https://invisioncommunity.com/forums

"(NE) browser-update.org integration" will provide you with the ability to present a notification to users of "out of date", insecure and/or unsupported web browsers, providing those users with guidance on how to update their browser. Notification functionality is provided by https://browser-update.org/, based on the configuration elements enabled in the settings of the plugin or application. Plugin (free) IMPORTANT: Support for the free plugin is strictly limited to the following: guidance on configuration, via direction to the relevant information on https://browser-update.org/ support for the code used within the plugin only, which is: a hook on the core -> front -> global template, to implement the relevant code to load the browser-update JS code and implement the configuration applied via the plugin's settings a settings page to allow you to configure the integration Application DEMO: Test mode enabled, checking for IE only

Ignore - too early in the morning.

We (your peers) can't tell you - an IPS employee might be along at a later point though. Log a ticket with support.

No. "I've noticed that the same password you use on your account is used on adminCP which means someone can get full admin access to the site just by finding out your user password." So don't use the same account for front-end and back-end. Or protect your account by ADDING A SECOND FACTOR OF AUTHENTICATION as mentioned.

Log in to your ACP - type 2fa in to the search bar, click the result.

Enable 2FA. Use different accounts - one with no Admin privileges for the front-end, one for the ACP - with different passwords.

OK - if you have made the suggested permission change and it has had not had the above effect, log a ticket. I'm happy to check it if you send me ACP credentials via PM.

Works fine - so maybe you could explain what you mean by 'hide' in that case?

Possibly reactions made to deleted content prior to deletion - these aren't removed. If you want to see if it is a bug, recount the user's reputation in the ACP and see what the result is - then log a support ticket if needed,

given = ones given by that person to others? Received = ones received by that person from.others?

So maybe make the sidebar sticky so that it is always in view? Edit core -> front -> global -> sidebar, and add data-ipssticky to the opening div: <div id='ipsLayout_sidebar' class='ipsLayout_sidebar{$position} {{if !( isset( \IPS\Output::i()->sidebar['contextual'] ) && trim( \IPS\Output::i()->sidebar['contextual'] ) !== '' ) && ( !isset( \IPS\Output::i()->sidebar['widgets']['sidebar'] ) || !\count( \IPS\Output::i()->sidebar['widgets']['sidebar'] ) ) && \IPS\Dispatcher::i()->application->canManageWidgets() && !$adsForceSidebar}}ipsLayout_sidebarUnused{{endif}}' data-controller='core.front.widgets.sidebar' data-ipssticky>

What's the error? December 5th is just over 9 months later than February 11th, yes...and so on. The 'x weeks/months later' is comparing the date of the post AFTER that line to the one BEFORE that line.

Group setting, "Can report content?"

That's because the task to check things ran...