Apfelstrudel

The topic can be closed. I have solved it on my own.

Hello team, We have been using the archive function for a long time and it has always worked well. However, since the beginning we have never changed the settings for the filter. Today, however, we have changed the settings from >15 years to >12 years, so three more years should be archived. The problem now is that since this change the archive function no longer archives. The cron job runs through without doing any action. If you unarchive an already archived topic from the archive, it works. You can then change someting in the thread. However, if I set it to “archive” status again, it remains unarchived. Also this feature worked fine in the past. In my opinion, changing the settings has caused a malfunction. We only changed the number from 15 to 12 and made no other changes. What could be the problem? Thank you for your help. Best regards

Hi Daniel, Thanks a lot for your quick help. I swear I did this twice, but it didn't bring any change. However, the main thing is that it works again.

It also seems that some javascripts are no longer working. Pull downs etc. can no longer be opened. I already cleared the system cache.

Hello, I updated to the latest version 4.7.16 today. But after the update, the editor no longer works. When I try to click on the reply box or the reply button, the editor does not open. I have also noticed in the backend that all editor fields are simply displayed as an empty box (without content). How can I fix this problem?

Hello Jim, is this bug really such a small problem that it will only be fixed in the next release? If basic functions of the UX for navigation are broken, I think it's important enough that it should be fixed in a patch. After all, you can't switch to other pages. This bug was the reason for me today why I didn't start the update to .16.

https://github.com/disposable-email-domains/disposable-email-domains https://github.com/disposable-email-domains/disposable-email-domains/blob/master/disposable_email_blocklist.conf https://gist.github.com/adamloving/4401361 I don't know if you have considered them yet. I also found a provider of a huge disposable email domains list. https://emailverification.whoisxmlapi.com/disposable-email-domains/

Interesting to hear, but I used Google's top search results for "10-minute emails" or "temporary emails". Maybe I should look on page 10 of the results page to use a lesser known provider. 😄 But seriously now, if the problem mentioned by opentype is like this, then the list of these providers should be optimized 😉.

Hello, today we upgraded to the latest release and immediately activated the "blocking disposable emails" feature. (btw, very good idea 😉) We did three tests with 10 minute or temporary email providers and in every case I was able to finish the registration and confirm my email address. Did I do anything wrong?

Hello Marc, thanks for your help. I already got an email from support. So it was not necessary to start the upgrader.

Where did I say I expected you to start the upgrade? 😉 I just mentioned that it would make some discussions easier if you looked at the problem in the backend right away. Anyway, thanks for your information about the open bug report. We will wait to upgrade until the bug is fixed. 🙂 Just one last question. Will this bug then be fixed in a future version or will the current build be changed? So do we have to skip the 4.7.12 upgrade then? Thanks in advance for a short answer.

Does this mean you are aware of this problem and will fix it? Because I also do not understand what you can not understand about my post. The upgrader could not start because this profile field is missing. Sorry to be a bit direct, but if you, dear Marc, would at least occasionally make the effort to look into the backend, some question loops could be avoided and some questions would not even arise. This is only a small excerpt from the experiences I was allowed to make in the last 5 years 😉.

The profile fields were removed normally via the backend a couple of weeks ago. The upgrade process brings the following error message in step 1: "There are some problems with your database which need to be fixed before you can start the upgrade". Then when I go to "Get Support" in the backend and look at the database error, it brings me the following suggestion: "ALTER TABLE 'ips_core_pfields_content' ADD COLUMN 'field_1' MEDIUMTEXT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci NULL;" Why should I add profile field #1 again when I don't need it anymore? And even if I would run this query, what about the pfields data table that also contains info about the profile fields? Wouldn't that cause other problems? I heard from another forum owner that this could happen because the profile field #1 is defined in install.sql. I didn't see any warning during the profile fields deletion process that we are not allowed to delete field #1 😉.

Hello, we wanted to upgrade to 4.7.12 today, however the database check found a problem before. Apparently it is because the profile field with ID 1 is no longer present. FYI. We recently removed that very profile field because it contained information about AIM that no one uses today anyway. Likewise, we removed some other old profile fields that no one needs anymore. Our instance originally came from a vB import. How to do the upgrade now?

Where are these privacy and PII features here in this community? I can't find them in the "Security and Privacy" section within my profile settings.