Kirill N

1 hour ago, Marc Stridgen said:

You should be able to see statuses on anyones profile without the need to add anything further. Please could you clarify?

I’m looking for the page with just status updates from everyone.

1 hour ago, Ryan Ashbrook said:

The statuses page has not existed for many years - it was replaced with the Activity Stream system in 4.1.0.

How do I create a stream that’s just status updates?

After upgrading to 4.7, I can no longer see the /statuses page — any idea how to bring it back?

Thanks!

Finally working! Thanks everyone!

1 hour ago, Nathan Explosion said:

That it may be, as it is a separate server software - but is the PHP extension for Redis loaded?

Go to the Support page in the ACP, click on the PHPInfo button and review what is loaded - no redis, contact your host.

Thank you for the response! Here’s what my phpinfo says:

The “Data Storage Not Working” error is now gone, but “Cache Not Working” is still there.

Hi again! 

My upgrade went smoothly, but I’m getting the following errors:

Data Storage Not Working
Cache Not Working

The Redis option is greyed out and says “In order to use this method, the Redis extension must be installed on your server.”

I contacted my host and Redis is installed and working.

Any idea what is wrong?

6 minutes ago, Stuart Silvester said:

This isn't using proper backticks. You can remove this line

Oh wow, thank you.

It worked!

23 minutes ago, Marc Stridgen said:

You need to take a look at your conf_global.php file, as something is not correct in there. Have you manually changed something in there?

This is what it looks like. I haven’t changed it in years.

<?php
$INFO['sql_driver']			=	'mysql';
$INFO['sql_host']			=	'localhost';
$INFO['sql_database']			=	'***';
$INFO['sql_user']			=	'***';
$INFO['sql_pass']			=	'***';
$INFO['sql_tbl_prefix']			=	'';
$INFO['sql_debug']			=	'0';
$INFO['sql_charset']			=	'';
$INFO['board_start']			=	'1318618567';
$INFO['installed']			=	'1';
$INFO['php_ext']			=	'php';
$INFO['safe_mode']			=	'0';
$INFO['board_url']			=	'***';
$INFO['banned_group']			=	'5';
$INFO['admin_group']			=	'4';
$INFO['guest_group']			=	'2';
$INFO['member_group']			=	'3';
$INFO['auth_group']			=	'1';
$INFO['use_friendly_urls']		=	‘1’;
$INFO['_jsDebug']			=	'0';
$INFO['mysql_tbl_type']			=	'InnoDB';
$INFO['use_memcache'] = '1';
$INFO['memcache_server_1'] = '127.0.0.1';
$INFO['memcache_port_1'] = '11211';
$INFO['sql_utf8mb4'] = TRUE;
?>

10 minutes ago, Marc Stridgen said:

If you are getting a blank page, please check your PHP logs to see what the actual error is

Hi Marc!

This is the latest error:

[03-Aug-2023 10:34:39 UTC] PHP Fatal error:  Uncaught Error: Undefined constant "‘1’" in /home/***/public_html/conf_global.php:20
Stack trace:
#0 /home/***/public_html/system/Settings/Settings.php(56): require()
#1 /home/***/public_html/system/Patterns/Singleton.php(41): IPS\_Settings->__construct()
#2 /home/***/public_html/system/Http/Url.php(771): IPS\Patterns\_Singleton::i()
#3 /home/***/public_html/system/Http/Url.php(248): IPS\Http\_Url::baseUrl()
#4 /home/***/public_html/system/Request/Request.php(276): IPS\Http\_Url::createFromString('https://***...', true, true)
#5 /home/***/public_html/system/Log/Log.php(106): IPS\_Request->url()
#6 /home/***/public_html/init.php(1034): IPS\_Log::log('Error: Undefine...', 'uncaught_except...')
#7 [internal function]: IPS\IPS::exceptionHandler(Object(Error))
#8 {main}
  thrown in /home/***/public_html/conf_global.php on line 20
 

2 minutes ago, Nathan Explosion said:

In that case, you need to ensure that your PHP 8.1 installation meets the requirements. Download the following, upload it to the root of your IPS install and run it in the browser, correcting any flagged issues (most common one is that the SQL extensions aren't enabled)

Already did this, everything is green.

1 minute ago, Nathan Explosion said:

Correct - you need to switch to PHP 8.0 or 8.1, but not 8.2

Correct - because 4.5 doesn't support PHP 8.x

Leave the ACP and instead go straight to https://domain.com/admin/upgrade to begin the upgrade.

Thanks for such a quick response, Nathan.

/admin/upgrade gives me a blank page with any PHP version, including 8.1.

I believe I’m having the exact same issue as this client — would appreciate it if someone from IPS could open a ticket for me.

Hello,

I’m trying to upgrade my community to the latest version and after uploading the files, this is the error I’m seeing in my Admin CP:

We're sorry, but a temporary technical error has occurred which means we cannot display this site right now.
syntax error, unexpected '->' (T_OBJECT_OPERATOR)
You can try again by clicking the button below, or try again later.

I believe it has to do with the PHP version, but when I switch the server to PHP 8, the site won’t load at all.

Any ideas on how to fix this and proceed with the upgrade?

21 hours ago, Marc Stridgen said:

Are you running any caching there at all?

Hi Marc,

After a few hours I managed to get in. Looks like caching was indeed the issue.

Thank you!

5 minutes ago, Marc Stridgen said:

Could I confirm you have tried manually entering these? By this, I mean not using any password manager or anything? This would only show if the password is incorrect. Also, has anything changed just prior to this?

Thanks for the quick response, Marc!

Yes, I entered the details manually.

Not only that, but once that first happened, I completely removed the installation and installed it again (with different details and a fresh database) and the same thing happened.

Also, the fact that the exact same message (“14 minutes”) appears regardless of how much time passed, makes me think that something is definitely wrong haha

Hi everyone,

I just made a test installation and when I try to log in to the AdminCP, I get the following message:

Your account has been locked. Try again in 14 minutes.

I’m 100% sure I’m entering my login details correctly. But even after 14 minutes, same message. In fact, it doesn’t change at all and always says “14 minutes” no matter how much time passed.

Any help would be appreciated!

Hi,

I’m having a security issue with my website — over the past few days, at least 4 inactive accounts were hacked and used to post spam message.

I’m running a pretty old version (4.6.1) but unfortunately I’m not able to upgrade until next week—is there anything you would recommend doing in the meantime? Perhaps this is a known current issue.

Any help would be appreciated, thank you!

1 minute ago, Luuuk said:

As stated, you can use the browsers inspector for this purpose. You can see all currently loaded CSS with their content in the inspector.

In Chrome Dev Tools > Network > select CSS only > click a selected request containing a name of CSS > Preview:

Thank you, I appreciate the help. I’m aware how the Chrome inspector works, the issue is that it is not very helpful when it comes to responsive elements, and figuring out how something works through developer tools takes 100x times longer than just searching for a class in the editor.

15 minutes ago, Charles said:

We didn't make this up 🙂 we modeled it after literally every SaaS service out there.

I might submit that an "upgrade-friendly solution" is 100% what we should always choose.

What is the reasoning for not making the CSS at least viewable in the editor?

15 minutes ago, opentype said:

This is EXACTLY what makes it the right solution. This file was specifically created for this purpose. It even says so when you open the file. 

/**
 * This file is for your custom CSS.
 * This file is not modified or overwritten during upgrades
 */

This describes the purpose and why changes should only be made there.
You have no argument against that, because there is none. You are essentially just in denial. You are saying “if I was allowed to do it the wrong way in the past, you better let me keep doing it the wrong way”. And ironically, this practise is NOT an argument to revert the change, but instead an argument to make sure that this practise is indeed being stopped. 

That makes it the Invision-preferred solution or upgrade-friendly solution, not the right one.

Saying that it’s the right solution because it makes upgrades easier is like saying that cutting off your arm is the right solution to losing body weight.

But clearly I’m in the minority here and the Invision stuff will (rightfully) do whatever they please so arguing is pointless. This new version just isn’t for me.

2 minutes ago, opentype said:

It was always wrong though. You would change a core file and so every future update of that file would cause an unnecessary conflict. Adding an override in the custom.css was always the right solution. So, the change just prevents you from doing it the wrong way. 

Fixing something is always the better option that patching something.

Just because the custom file doesn’t get updated this way doesn’t make it the “right” solution.

2 minutes ago, Jim M said:

custom.css is loaded last so typically, won't even need the !important. I would advise reading through some CSS documentation if you are unfamiliar with how selectors get inherited and overwritten from stylesheet order.

The point is, editing something as minor as image size should not be this complicated and should not be done by adding multiple lines of code on top of existing code.

Creating a custom theme should not require pretty much re-writing the existing css from scratch.

2 minutes ago, Marc Stridgen said:

You would add a selector for ipsUserPhoto_large to custom.css. It needs to be pointed out that what you have suggested there that would take a short amount of time, was not the recommended way of changing things such as this in any version.

Would the code be

.ipsUserPhoto_large {
    width: 120px !important;
    height: 120px !important;
}

?

6 minutes ago, Jim M said:

It's a little more work but simply re-sizing your browser window to the correct size will show the responsive CSS in use. I personally work on breakpoints when it comes to these things so work on one window size at a time (e.g. mobile, tablet, or desktop) and it is not cumbersome.

Additionally, you can use the "Source" tab in the browser inspector to see the full source file.

If you would like to review the CSS, our self-hosted customers still have access to Designer's Mode which allows you to do so.

It’s not a little more work — something that used to take literally 10 seconds would now require to writing multiple lines of code.

Just to illustrate, let’s say I want to change the size of userpics in topic view from 90x90px to 120x120px. Before 4.7, I could simply search for “ipsUserPhoto_large” and change “90” to “120”. Takes about 20 seconds.

What’s the correct way of doing that in 4.7?

This was such a bizarre choice. I now pretty much have to re-write half of the theme AND keep everything in one file AND do it without any reference.

Ridiculous.

2 minutes ago, Stuart Silvester said:

Personally, when I'm theming or updating CSS for something on my site, I'm in the browser inspector for most of time. Looking at how the relevant rules interact with each other and determining which change I want to make to achieve my goal.

Browser inspector isn’t very helpful when it comes to responsive elements. Not to mention that it takes 10x more time than just searching for the element in the theme editor.

On 9/15/2022 at 11:05 PM, Stuart Silvester said:

You should be adding any custom CSS to the custom.css file instead of editing the CSS distributed by other apps. You'll only give yourself headaches upgrading them in future.

That’s understandable but we need to be able to VIEW them to know what we are supposed to edit