πŸ‡ΏπŸ‡¦South Africa @Gomez_in_the_South

Account created on 14 June 2007, about 17 years ago
#

Recent comments

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Hey @jwjoshuawalker - unless I'm mistaken, commit 51ce897a isn't included in the 3.0.0 release?

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

The commit I added was just to pull in the latest dev branch changes and fix the associated merge conflict.

The new tests seem to still be failing, though I didn't piece together what may need to be changed in the CSV Parser to resolve this.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Gomez_in_the_South β†’ made their first commit to this issue’s fork.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Thanks to all involved in fixing this.

I agree that it would be great to have a new release to include this.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Whilst the earlier fix was merged, this was only to the 3.x branch, and the commit was never included in the 4.x branch.

Due to this, I encountered the same issue as originally described, using Drupal 10.2 and EasyChart 4.0.9 (with Layout Builder).

I have attached a re-roll of the earlier patch, but for 4.x.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Thanks for merging this, we've been using this patch for a while.
I look forward to the next release that will include this.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

The attached patch adds the license url as: https://www.gnu.org/licenses/old-licenses/gpl-2.0.html, which matches the description that was in the library file.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

I came to this thread after seeing this error. Running the steps mentioned in #27 did resolve it.
To answer @DamienMcKenna's question - no - there were no config changes present after running the entity updates.

I have also been looking at the 2.x branch, which I understand doesn't have this issue.
I was however having issues with the upgrade to 2.x (as mentioned here πŸ› 'rh_action' not found Active ). I seem to be able to avoid those issues by first fixing this issue with the entity updates whilst on 1.x.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

I also encountered this error updating from 1.0.0-beta11 to 2.0.0-alpha5.

I was able to resolve this by going to the Rabbit hole configuration (/admin/config/content/rabbit-hole) and then for each entity, clicking "Configure" and saving it again.

After doing this, and running the updates again, the `rabbit_hole_update_8106` step completed ok.

(I have seen another error further on, with `rabbit_hole_update_8112` - "[error] SQLSTATE[23000]: Integrity constraint violation", but I'll raise a separate issue for this)

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

@jwjoshuawalker - would it be possible to get a new release with this patch included?

It would make it a lot easier for us to use composer to get the right dependency versions.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Pleasure, @ytsurk.

Would it be possible to get a new release? Otherwise other users may come across the same problem.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

I came to this module with the same expectations as other posters, and agree that this could be clearer on the module homepage.

I would propose adding this section:

<h2>Drupal 9+ features overview</h2>
<p>The following validation rules are currently included:</p>
<ul>
<li>Equal values on multiple fields</li>
<li>Compare two fields</li>
<li>Require at least one of two fields</li>
<li>Require at least one of several fields</li>
</ul>

Which would look like the screenshot attached.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

We were previously using the patch from #81 in our Drupal 9 site.
After upgrading to Drupal 10 we found that the newer patches (tried #125, #166) lead to an issue where unpublished menu translations were still being shown (and in some cases, the incorrect translation was showing).

To fix this, I've taken the `hasTranslation` function from #81 and added it to #166, see the attached interdiff for details.

Apologies if this distracts from the longer term solution that is being progressed in this post, but sharing in case it is useful to others.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

I'm also using Drupal 10.1.x, whilst still staying on Seven theme (for now).
The Media directories UI with the Seven admin theme appears completely broken, the size of the thumbnails was wrong, there was no tiling, and it wasn't useable.

I came to a similar solution to murphyW, adapting some of the styling rules from the previous version, and hacked a few other CSS overrides to get it to appear close to how it did before.

I only found murphyW's patch afterwards, which I have found fixes some, but not all of the styling issues I was finding. As such, I thought it worthwhile to still attach my version, in case it helps anyone else in a similar situation.

It's important to note that both patches attached to this issues are a temporary solution, and anyone using either one should:
- only use it if you're on the Seven theme (or want to see if it helps an issue with another legacy theme)
- not expect this to be merged
- plan to upgrade to Claro/Gin or similar in the near future

Perhaps the maintainers should change the status of this issue to "Won't fix"?

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

Attached patch adds the license url as: http://opensource.org/licenses/mit-license.php, which I had seen referenced in other modules.

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

It would be great to get a 2.0.3 release.

In our case we're looking forward to have #3293275 included, which was merged back in December (shortly after the 2.0.2 release).

πŸ‡ΏπŸ‡¦South Africa Gomez_in_the_South

We were also having an issue when creating translations for a newly installed language.

When adding a new translation we'd get the "Non-translatable fields can only be changed when updating the original language."

Patch #16 resolved this issue for us, so +1 RBTC.

[Drupal 9.5.3, Rabbit hole 1.0.0-beta11]

Production build 0.69.0 2024