🇫🇷France @ohmdesbois

Hello,
I encounter the same problem after updating to version 12.3.
Opensocial content does not have a creation date by default.
Previously, the date of creation of event, topic, page, etc, was entered on today's date by default.
Custom content does not have this problem.
Has anything changed about this?
THANKS

ohmdesbois → created an issue.

ohmdesbois → created an issue.

Hello @endless_wander,
Thank you for your reply.
I tried on simpletest and it works.
my problem (and possibly others) seems to come from the fact that I installed recurring_events on an existing profile (opensocial) which uses "events" functions in its "social_event" module
I tried on a new install of Opensocial and the annual instances are not created. The other recursion periods work and there are no errors in dblog.
The question of how to couple these two modules would not arise if it were possible to create instances of an existing event type. But I haven't found any information on this subject and it would be the subject of another issue.
thanks again
I'll move the topic to resolution

ohmdesbois → created an issue.

I am well aware that this issue is certainly a duplicate, but I would like to have a clear vision of the problem.
It seems to me that the related issues revolve around the same problem.
Would it be possible to have a synthetic explanation, a plan or a procedure to resolve the problem?
thank you for everything

ohmdesbois → created an issue.

ohmdesbois → created an issue.

ohmdesbois → created an issue.

ohmdesbois → created an issue.

I tried a new installation and, after updating the modules, the database update went well.
On an existing site updating version from 11 to 12 returned the same error indicating missing updates: user_post_update_update_roles.
Drush ws reports: Error: Class "Drupal\variationcache\Cache\VariationCacheFactory" not found in Drupal\Component\DependencyInjection\Container->createService()

Since this is certainly linked to one of the installed modules, i do the following :

1. went back to version 11,
2. updated the modules to the appropriate versions (not necessarily the most recent),
3. deactivated modules which seemed to pose a problem during updated composer.json (in my case fontawesome_menu_icons),
4. did an update of the database,
5. Adjust composer.json so that it executes
6. went back to version 12
7. make adjustments to composer.json
8. in my case : "composer require drupal/symfony_mailer",
9. composer update
10. drush updb

the update was carried out normally.

hope this is helpful, have a good day and don't give up.
Thank you Opensocial!

The update to version 12.0.0-rc6 went without any problems on my side. Several composer updates were necessary

ohmdesbois → created an issue.

For my part, when updating from social-11.11.3 with "goalgorilla/open_social": "~12.0.0-rc4" in the composer.json, the command composer why-not drupal/color ^1 returns

BaseDependencyCommand.php line 98: Could not find package "drupal/color" in your project

if I use "goalgorilla/open_social": "~12.0" in the composer.json, the social version 12.0.0-alpha2 is used
Thanks

I'm digging up this issue, because, since the last update, I get the same error when editing a user, even if the unique nickname box is not checked
The commerce module is not installed, so I have not tried the patch.
I tried to delete the field, but the result was catastrophic.
A track ?
THANKS

Good morning,
this problem seems to persist
and even by publishing a new album in a group with "community" visibility it is visible to everyone in the "explore" view
Thank you for your answer, or I missed something
Brest regards

ohmdesbois → created an issue.

ohmdesbois → created an issue.