future @null is going to hate you 😄
@VaporCharlie has joined the channel
@Chris Kreft has joined the channel
@Chris Kreft this isn't a very helpful question I'm sorry. I'm certain it has been done, but are there some particular issues you're having trying to do this? Or are you just interested to know if it can be done? (yes it can 🙂 )
Just wondering if there is any BuildTask existing or if i am missing something. Seems Like there is no "out of the box" way. Unfortunately all elements are gone after upgrading. Seems like it can be done with some DB Queries...
Ah, I see. Is this just with custom block types, or any and all blocks?
oh gosh, there's no legacy yml at all :/
@Chris Kreft - if you update the
ClassName field of the elements table to reflect the now fully qualified classes, do the elements show up?
Or is the problem bigger than that?
Hi @Nightcrawler Thanks for your reply. Unfortunately not - its with all elements. It's probably because of the removal of widgets... Maybe the queries help, which some posted earlier in that channel.
@Chris Kreft maybe you can also add some of your queries to https://github.com/dnadesign/silverstripe-elemental/blob/4/docs/en/upgrading_to_4.md if you find out how it works?
i'll give it a try
> oh gosh, there's no legacy yml at all 😕 i think that's because it would be a little misleading to indicate that the upgrader can upgrade this module safely, since we changed a lot from elemental 2 to 3/4
Yeah, it is quite different. Just been a long time since I looked at it.
Is there a way, using
ElementalAreaExtension to display the name of the Elemental Area itself within the CMS - i.e. display the keys of the relevant
- private static $has_one = array(
- 'BeforeContentArea' => ElementalArea::class,
- 'AfterContentArea' => ElementalArea::class,
- 'FeaturesArea' => ElementalArea::class,
- 'HistoryArea' => ElementalArea::class,
Add a headerfield before it.
Has anyone got Elemental blocks to be indexed in Solr? Like as standalone classes, not using
For the life of me, I cannot get these things indexed (while checking the core itself in the Solr UI)
I'm using @Firesphere’s module with the "fulltextsearch" compatibility module, which may or may not have an effect..