taz.de

hi @teraßyte - now as i know thet there is no such setting i would try to find out where the magic happens and write a hook or query to change that habit. if i run out of time, i'll contact you, thanks.

hi, how could i change notiofiucation settings for all users or all users of a certain group so that they e.g. don't get any notofocation that their message was approved?

i understood that. using the debian packages as a guide for switching php versions was just a suggestion. because ipb asked us to update, we upgraded to php8. first to 8.2, then to 8.1 because of problems. i am glad to hear that you don't have any issues what is good for you. we had the above issues with the debian 8.2 packages which lead to apache segfaults on our server when /admin/?app=core&module=support&controller=support was called.

dear marc, nice to hear from you; php8.1 is not in the official debian repositories. they (our admins) hate it when we install php with using sury. most likely because safety and other standards. when you officially support only 8.1 (and when we have problems like my colleague described above) we can't use the 8.2 debian php package and have to install 8.1 from sury. or the admins have to build an own package. i think ipb/ips is the only software package we use which forces us to do such things. i hope you are well, best regards.

Was that meant as an answer? That is what @Stuart Silvester already wrote and was not questioned by our comments.

just to let you know: for us and especially our admins, it would be helpfull if you could synchronize the supported php version with the one supported by the actual stable debian packages.

One issue with PHP 8.2+ as far as I can tell, is that in Dev mode some pages act funny, with a bunch of our plugins that use the apparently standard IPB construct 'return \call_user_func_array( 'parent::' . __FUNCTION__, \func_get_args() );', throwing deprecation and Exceptioning out of most pages. You can of course disable deprecations in php.ini (```error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT```) But then the 'get support' page doesn't load, unless you hack some PHP code like this into the top of the core support.php file (```error_reporting(E_ALL | E_STRICT);```). It's possible that under 8.2 / dev / prod mode it's also throwing other errors. Finding a php.ini error_reporting config that works for both use cases does not seem to exist. Looking forward to PHP 8.2 support soon.

we are still searching. there was another user whose content moderadtion was removed even if he had just 1 post and we have confuigured 30 posts minimum. content count is 1. but when i switched off javascript i see this 'content count' table in the user profile: i am wondering why there are entries with a count of 0 even if the user is a member just as 1 day. regards!

merci

Sorry Marc, wasn't there an option to recount content count? is that still there? And if, where?

yeah i know i know unfortunately it is as it is, thanks for the idea with rthe groups, i will check that. if you have a hint where in the code the content count is calculated, that would be helpfull and you don't need any admin access for that 🙂 regards, ulf

hi, okay. we don't know what content could that be which counts that counter down since we are not using IPB as frontend. the count is reflected on the profile but as you see i n our screenshots the count is on 11 and nevertheless the last posts were submitted even if the minimum approved posts are on 30. there wasn't any modifications. we just are updating since IPB 3.x mud never modified s.th. on the content count. also we can provide you with any information you like but not with admin credentials to our systems. we have to explain that over and over with every support request. i think we have to analyze that on our own and write s.th. what only deals with posts. regards, ulf

hi, we are posting via REST API into our IPB. the current setting from members/groups/content is the current setting from /forums/forum/Posting settings is what we want is that the user has to write at least 30 APPROVED posts until the content moderation will be removed. but in fact that happens mostly after under 30 posts, in some cases after under 10 posts. for example the following user was suddenly able to post (where in our version "GESAMTE INHALTE" is written, in the english origininal there is written "POSTS"): what could be the reason for that? could it have to do with the "content count"? does it include other things than posts? which exactly and where in the database i could check that count? ma be it possible that content count doesn't work reliably with the REST API? regards, ulf

hi, i am interested in this to use it with the actual version of ipb in the same way as chrisvanmeer wished above (in 2018): i would like to lock topics in a forum 7 days after the topic was created. is that included meanwhile? regards.

hi. i tried woodsmans pretty well described steps on page 1 of this topic. i tried to get a clean upgrade from the productive server onto a test server. for me, the following steps were necessary in addition to that before the upgrade: - i cleaned up my default language pack (which was in a mess) as described here: https://www.exactservers.com/topic/477-how-to-restore-the-english-us-language-pack/ - in the adminCP under system/system/settings/general configuration, check if the settings in "Path to 'upload' directory" and "Upload URL" are correct and if not, change them and click on change settings.