TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → made their first commit to this issue’s fork.
Fix @FMB
TeeBeeCoder → created an issue.
@James Hawthorn-Byng, @alex9000,
I wonder if this could be due to the fact that your server doesn't have algolia as its machine name? Can you give me some information so that I can check that this is not linked to https://www.drupal.org/project/search_api_algolia/issues/3343995 🐛 Server machine name must be algolia? Needs review ?
Thomas.
TeeBeeCoder → created an issue.
Hello,
I've fixed the bug and now you don't need to have a server with the name Algolia for the deletion to take place.
Thomas.
TeeBeeCoder → made their first commit to this issue’s fork.
The rest of the migrations were ported, please find the list below:
- * Nodes
- * Users
The bug has been resolved since this patch was created.
The proposed solution also creates a problem, because if the cookie is sent back to HubSpot empty, we receive a message in return. Please see below.
HTTP error when submitting HubSpot data from Webform "XXXX":
{"status":"error","message":"The request is not valid","correlationId":"xxxxxxx","errors":[{"message":"Error in 'context.hutk'. '' is not a valid Hutk","errorType":"INVALID_HUTK"}]}
@sanduhrs, I am unable to replicate the reported bug, and I am confident that the functionality is operating as intended. Consequently, I am closing the associated issue.
Should you succeed in reproducing the issue and can provide more specific details, I kindly request that you reopen the ticket and elucidate the steps you took to encounter the bug, enabling us to address and rectify the matter promptly.
@sanduhrs, I am unable to replicate the reported bug, and I am confident that the functionality is operating as intended. Consequently, I am closing the associated issue.
Should you succeed in reproducing the issue and can provide more specific details, I kindly request that you reopen the ticket and elucidate the steps you took to encounter the bug, enabling us to address and rectify the matter promptly.
TeeBeeCoder → made their first commit to this issue’s fork.
TeeBeeCoder → made their first commit to this issue’s fork.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
I have a solution for this query, I will just check the rest to propose optimizations on the whole project as it's mainly a problem of indexes not being set properly.
I think that we can close this one as it is a duplicate of https://www.drupal.org/project/l10n_server/issues/3338991 📌 Export page Needs work .
TeeBeeCoder → made their first commit to this issue’s fork.
Thank you very much!
TeeBeeCoder → created an issue.
Yes, no problem with the command. We were experiencing issue with it, but somehow it was related to MySQL.
Thank you @Artusamak for reviewing it!
TeeBeeCoder → made their first commit to this issue’s fork.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
@FMB as agreed today, I'll do the update to D10.
It should be fixed now. There are some styling issues, but I think that fixing them later is the way to go.
@FMB,
I found a way to reproduce the alert box on the D7 version, please see attached file. I think that the behavior is the one expected, but I'm not sure about the UX.
Steps:
- go on https://localize.drupal.org/translate/languages/fr/translate?project=dru...
- click on the pen
- see the alert box
@FMB, I updated the patch and I also opened a MR on GitLab if needed.
Hope this help.
TeeBeeCoder → created an issue.
TeeBeeCoder → created an issue.
@FMB,
I'll check it!
Hi, I tested the patch on a fresh instance and after having enabled the module, no errors in DB log and the file was generated correctly.
So LGTM.
Thomas
TeeBeeCoder → created an issue.
TeeBeeCoder → made their first commit to this issue’s fork.