MythonPonty

/* Blogs */ li:nth-child(2) span.ipsOffCanvas__label::after { content: "Pro"; display: inline-block; background: #00cc66; padding: 2px 5px; font-size: 10px; text-transform: uppercase; border-radius: 4px; color: black; font-weight: bold; margin-left: 10px; } /* Downloads */ li:nth-child(6) span.ipsOffCanvas__label::after { content: "Neu"; display: inline-block; background: #FFB343; padding: 2px 5px; font-size: 10px; text-transform: uppercase; border-radius: 4px; color: black; font-weight: bold; margin-left: 10px; } Here only this works, currently. Maybe @Ehren have a better idea for the mobile view ?

You can do it with this short snippet li[data-navapp="blog"] .fa-solid { color: #007BFF; font-size: 16px; transition: color 0.3s ease; } li[data-navapp="blog"]:hover .fa-solid { color: #FF5733; }

/* Menütags */ li[data-navapp="blog"] span:nth-child(2)::after { content: "Pro"; display: inline-block; background: #FFB343; padding: 2px 5px; font-size: 10px; text-transform: uppercase; border-radius: 4px; color: black; font-weight: bold; margin-left: 10px; letter-spacing: 0em; } li[data-navapp="gallery"] span:nth-child(2)::after { content: "Neu"; display: inline-block; background: #00cc66; padding: 2px 5px; font-size: 10px; text-transform: uppercase; border-radius: 4px; color: black; font-weight: bold; margin-left: 10px; letter-spacing: 0em; } I did this for my testsite... here you control which app it should affect

I am very grateful for what the great team has achieved. And I don't want to debate how others have already done it. I just mentioned that it would be great, because this function would bring really great added value. But I'll go with what comes next... I just wanted to point out that this function is “super” and would bring added value to all community owners.

I have to speak up, it's not a moan or a groan, but just to raise my finger once and say that if I could wish for it, I would love it if the function “assign topics to moderators” would also be available for Classic Hosting. The Community Experts okay, is nice to have. But we have a lot of posts that are moderated and it would be really helpful if we had this feature. Then we would know which posts are already under observation by which moderator. Otherwise we keep getting in each other's way. And once again... Thank you very much for the great update to the next level.

Hey guys. I hope everyone is as busy testing and experimenting as I am 🙂 Today I would like to test the “most helpful” and “Community Expert” function. The summary of posts works great, but I have not yet been able to get the system to the point where a user has received the “Community Expert” badge. Is it possible to provoke this so that you can see it live in Beta 6? What about the metrics ? How can i test this in my dev environment ?

Hey guys... I have a simple question. If I have 4.7.19 as a Live system and I install a new version in my development environment, then the settings in the admin panel of the development environment are set to default. Now I would like to export all settings from the “live system” and import them into the “development system”. I have not found a function for this. Can anyone help me? Why only 4.7.19 although this is the v5 beta discussion, simply because I will do an intermediate migration with my forum. I'm starting from scratch, but want to keep the settings.

Soooooo guys... I'm happy now. Short step list of what I did to finally use a working installation of 5.0.0 Beta 4. 1. fresh installation of 4.7.19 (without existing data) 2. conversion of data from the production environment to the new fresh installation environment. 3. standard procedure to upgrade from 4.7.19 to 5.0.0 Beta4. Exchange all files as supplied and then start domain.tld/admin/upgrade. Lo and behold, everything works perfectly and without any error messages. Now it's time to get down to business.

I had already tested it before with 4.7.18. I had the same result here. Perhaps an application is interfering in the background, even if it has been “deactivated”. Therefore, my plan would be to install a fresh installation with 4.7.19 after the release, migrate the data from the database once, and then perform another upgrade based on the fresh installation (without applications and plug-ins).

ok i'll give up... will try the last chance. Install a fresh 4.7.19 instance. Convert the productive site to the demo site, without any apps and so on, migrate the User, Forums... and so on, and try to upgrade again.

I have checked twice. All files were transferred according to Filezilla. Without any problems. However, the hottopics.php file is also not included in the v5 upgrade

@Jim M

After a second try i got the following message and this one on my start page

I'll try it again... 🙂

Hey Guys. Who of you can tell me the easiest way to upgrade from 4.7.18 in a short step-by-step list? I have tried to upgrade every time from beta 1 to beta 4 (v5). I go and copy all the new files into my old 4.7.18 environment. Then I start domain.tld/admin/upgrade and let the upgrader update everything once. After that, my start page is never accessible. I always get errors. For example this one A clean installation is not the problem, but currently the Converter isn't ready Is it necessary to uninstall all modules and applications before?

I've switched both Licenses long time ago, and my Communities works.

Biiiiig Thanks to you @Matt and the whole team. You've spend so much time last year... I'll check the upgrade for my community tonight (German Time) 😉

What about the possibility to convert / replace different Tags to aliases... Members could currently use for "love" similar words. e.g. Feeling Warmth of heart Devotion Intimacy Affection Passion I could well imagine that the different words for love could be combined into one main tag --> love. This would allow me to reduce many of the existing tags.

Check #Part 1 ✅ Check #Part 2 👉😃👈

Interesting... I also want to know how it works. Are the assignment details public or are they restricted only to the mod team?

perfect @Nathan Explosion Thanks for your information. Works now perfect.

Good Morning... I get following message after deleting members. (Project poeten.de) TypeError: IPS\forums\_Forum::setLastComment(): Argument #2 ($updatedItem) must be of type ?IPS\Content\Item, IPS\forums\Topic\Post given, called in /var/www/vhosts/httpdocs/system/Content/Comment.php on line 1360 (0) #0 /var/www/vhosts/httpdocs/system/Content/Comment.php(1360): IPS\forums\_Forum->setLastComment() #1 /var/www/vhosts/httpdocs/applications/core/extensions/core/Queue/MemberContent.php(107): IPS\Content\_Comment->changeAuthor() #2 /var/www/vhosts/httpdocs/system/Task/Task.php(54): IPS\core\extensions\core\Queue\_MemberContent->run() #3 /var/www/vhosts/httpdocs/applications/core/modules/admin/system/background.php(87): IPS\_Task::runQueue() #4 /var/www/vhosts/httpdocs/system/Helpers/MultipleRedirect/MultipleRedirect.php(93): IPS\core\modules\admin\system\_background->IPS\core\modules\admin\system\{closure}() #5 /var/www/vhosts/httpdocs/applications/core/modules/admin/system/background.php(138): IPS\Helpers\_MultipleRedirect->__construct() #6 /var/www/vhosts/httpdocs/system/Dispatcher/Controller.php(107): IPS\core\modules\admin\system\_background->process() #7 /var/www/vhosts/httpdocs/applications/core/modules/admin/system/background.php(42): IPS\Dispatcher\_Controller->execute() #8 /var/www/vhosts/httpdocs/system/Dispatcher/Dispatcher.php(153): IPS\core\modules\admin\system\_background->execute() #9 /var/www/vhosts/httpdocs/admin/index.php(13): IPS\_Dispatcher->run() #10 {main} Backtrace #0 /var/www/vhosts/httpdocs/init.php(1036): IPS\_Log::log() #1 [internal function]: IPS\IPS::exceptionHandler() #2 {main}

How could this be seen from the user's perspective? "Is it motivating to write more quality posts so that I appear in the summary", or can the user think "If I don't appear in the summary anyway, I won't write any more posts". I think the tool is nice... But users are sometimes strange in their decisions. How would you see that ?

One additional question about Reactions ! Do we have a rights management for reactions in v5? For example ! I want to use negative Reactions just for the moderation team and i don't want to use them global for all users. A warning is sometimes not the right tool and is too strict. I would rather just show a stop sign or raise my index finger as a warning.