teraßyte

@Daniel F New version is up. Just waiting for it to be approved now. 🙂 Changelog for new 4.1.2 version:

@Daniel F Yeah, I actually added something to catch that after I looked at the site but it looks like I forgot to release a new version with the fix. My bad. 😅 I'll release a new version in a few minutes and include also the change for the uninstall process while I'm at it.

For #1, if you've already changed the url in conf_global.php, then the home link is most likely hardcoded in the menu manager in ACP > System > SITE FEATURES > Menu Manager. Just edit the menu entry there. For #2 & #3 instead you need to update your storage setting path in ACP > System > OVERVIEW > Files > Storage Settings (button top-right) > Configurations TAB.

Not by default, no. A possible option is to: Adding the username in the editor. Click the 3 dots menu top-right of each post. Click the Share menu item. Copy/paste the link in the editor from the popup that appears and/or manually add the post ID from the share link itself. So yeah, not exactly the most user-friendly option. The only other solution would be a custom modification.

Just noticed an issue on a client's site when editing the default notifications options in ACP: LINK: https://www.domain.com/admin/?app=core&module=membersettings&controller=notifications&do=edit&id=dp42managefollow_dp4managefollowNotification === A configuration or server error has occurred EX0 Something went wrong. Please try again. === TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given (0) #0 /home/xxxxxxxx/public_html/applications/core/modules/admin/membersettings/notifications.php(185): in_array() #1 /home/xxxxxxxx/public_html/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\membersettings\_notifications->edit() #2 /home/xxxxxxxx/public_html/applications/core/modules/admin/membersettings/notifications.php(38): IPS\Dispatcher\_Controller->execute() #3 /home/xxxxxxxx/public_html/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\membersettings\_notifications->execute() #4 /home/xxxxxxxx/public_html/admin/index.php(13): IPS\_Dispatcher->run() #5 {main} Version 4.1.2.1 of the application; Suite 4.7.5; PHP 8.0.26.

Blog itself doesn't support paywalls, but maybe you can use the clubs feature and have them setup a paid club to access their content/blog.

I noticed the same issue on this very forum. Sometimes I get a notification that I have X unread comments when there's only 1 or 2. Chrome, Windows.

This guide should help you on where to find the url (or on how to create a custom RSS feed too in case):

@SUBRTX A 500 error can literally be anything. Considering it works with the default theme I'd say the issue is some kind of change in the custom theme, but I can at least point you in the right direction if I have the actually error log. Can you look up the exact error in your error_log file or in your server's control panel?

Until IPS adds the feature you can try checking out this modification instead: It doesn't exactly add a badge, but it does something similar.

That's not 100% true for self-hosted: For applications you can indeed download a copy of the folder from the server and you're done. For plugins however it's not the case: missing install/upgrade files, resources, javascript, etc. Manually re-creating a plugin's XML file after it's installed is a real pain. I received some requests for updating old plugins and since they didn't have the original XML file it was a really annoying process upgrading them.

9 months later... this still isn't fixed even with the fix already provided in the first post... 🙄

That page means there is some kind of issue with a MySQL query or the MySQL server itself. It should save a log in the /cache folder and you can look up the actual error there.

There doesn't seem to be anything wrong in the template itself at a first look. Maybe it's the template variables. Click on the Variables... button and post here the textarea content.

Yeah, the number of links should be displayed. If no lines are allowed the signature area should be disabled in the first place though. 😅

There's also a bug with the signature restrictions at the top of the page not properly listing them all though. The screenshot in the first post simply lists that "images are not allowed". It doesn't say anything about "number of links" or "lines of text" (which are both set to 0).

@Matt When the tables where all updated from mediumint(8) to bigint(20) for member ids in a past version, the upgrade skipped this step and only new installation used bigint(20) from that point on. If I recall correctly it was temporarily skipped because it could have caused issues altering big tables (mainly for big sites) in a minor (?) version. It was supposed to be added to the next major version, but it looks like it was never done until now. That's also when the code I pointed out in the other topic was most likely added:

Not currently. I made this based on a request and they asked to allow only admins & moderators to be able to see it. I can certainly look into adding a group setting for the next update though. I'll probably change the Yes/No setting to a radio option: No Administrators only Administrators & Moderators Specific groups only That way it should cover all options. 🤔

As Marc mentioned it's not possible by default. Until IPS adds such feature the only way would be a custom modification.

Was it a public application available in the marketplace or a custom one? If it's a public one it might help others if you post the name. 🙂

New converter application versions have the redirect scripts included in the code itself but older versions used to have php files uploaded separately on your server. Based on your log it looks like you indeed have one such old script which is most likely missing the latest changes: /forums/showthread.php Try removing/renaming that file, check if the errors stop, and also double-check if your old vB topic urls still redirect properly.

Looking at those logs you have several crashed tables that need to be repaired. In addition I also see that you're using MySQL 8.0 and I've seen a few people having issues with it. It would be best to use MySQL 5.7 or an equivalent MariaDB version instead.

There's no way to cancel an upgrade. You'd need to restore the backup made right before upgrading (as long as you took one).

Ran the query. Everything seems okay for now. 👍

Maybe you have a backup cronjob/task that runs on those specific days? That's something you should ask your hosting usually though. (Unless you're hosted on Cloud.)