enter image description hereexcuse me if I make few mistakes I am French.
I am trying to load a fixture on symfony but I don’t know why it doesn’t work.. it seems that my file AtelierFixture doesn’t recognise my Entity Atelier.php because when I start writing $atelier= new Ate..there’s no autocompleting and no automatic importation of "use App\Entity\Atelier" as it’s the case in the tutorials I’ve watched. I really don’t understand why.
So I have tried to write it manually but then when a run the command php bin/console doctrine:fixtures:load nothing is added to my database though it doesn’t display any errors.
I only have loading loading : App\DataFixtures\AtelierFixtures as you can see on the following pictures.
Could someone please bring me help I am so desperate, it makes me waste so mush time since yesterday whereas it’s for an important exam due in few days :( Thank you for your kind help!
Related
I am able to parse the markdwon with the help of remark and remark-html. How can I add syntax highlighting features for the code element?
I've been searched for TWO whole days trying to use remark/rehype ecosystem on syntax highlighting which is way more complex to use. I'm still working on searching, it's better to avoid remark/rehype ecosystem and try another method.
Here I share list of my search, just give you some subjective perspective so that you won't waste you too much time on things that not working. None of them will work as you expected, and their sample code are obscure or just broken codes.
https://github.com/remarkjs/remark-highlight.js
They move to support rehype. Are you a big fan of them wanna move as well?
https://github.com/sergioramos/remark-prism
You will get this error: Module parse failed: Unexpected character '�'
https://github.com/torchlight-api/remark-torchlight
They states on their website: 🚨 This client is still very much a work in progress. Please open issues! 🚨View it on github at github.com/torchlight-api/remark and this link is invalid.
https://github.com/rehypejs/rehype-highlight
It force you to use rehpye althought you can you remark-rehype for you to transfer easily. However, debug your code once you encounter some error will be helpless.
sample code use third-pary v-file to read file showing their code is working but not. and it reads html file not markdown file.
It's hard for you to grasp their concept to use their plugins to easily. It waste most of you valuable time to think what they think.
I give up remark/rehype ecosystem and stay away from them. Good luck! :)
Why some data on server-side are still stored in DBC files, not in SQL-DB? In particular - spells (spells.dbc). What for?
We have a lot of bugs in spells and it's very hard to understand what's wrong with spell, but it's harder to find it spell...
Spells, Talents, achievements, etc... Are mostly found in DBC files because that is the way Blizzard did it back in the day. It's true that in 2019 this is a pretty outdated way to work indeed. Databases are getting stronger and more versatile and having hard-coded data is proving to be hard to work with. Hell, DBCs aren't really that heavy anyways and the reason why we haven't made this change yet is that... We have no other reason other than it being a task that takes a bit of time and It is monotonous to do.
We are aware that Trinity core has already made this change but they have far more contributors than we do if that serves as an excuse!
Nonetheless, this is already in our to-do list if you check the issue tracker at the main repository.
While It's true that we can't really edit DBC files because we would lose all the progress when re-extracted or lost the files, however, we can modify spells in a C++ file called SpellMgr.
There we have a function called SpellMgr::LoadDbcDataCorrections().
The main problem while doing this change is that we have to modify the core to support this change, and the function above contains a lot of corrections. Would need intense testing to make sure nothing is screwed up in the process.
In here by altering bits you can remove or add certain properties to the desired spells instead of touching the hard coded dbc files.
If you want an example, in this link, I have changed an Archimonde spell to have no cast time.
NOTE:
In this line, the commentary about damage can be miss leading but that's because I made a mistake and I haven't finished this pull request yet as of 18/04/2019.
The work has been started, notably by Kaev. I think at least 3 DBCs are now useless server side (but probably still needed client side, they are called DataBaseClient for a reason) like item.dbc.
Also, the original philosophy (for ALL cores, not just AC) was that we would not touch DBC because we don't do custom modifications, so there was no interest in having them server side.
But we wanted to change this and started to make them available directly in the DB, if you wish to help with that, it would be nice!
Why?
Because when emulation started, dbc fields were 90% unknown. So, developers created a parser for them that just required few code changes to support new fields as soon as their functionality was discovered.
Now that we've discovered 90% of required dbc fields and we've also created some great conversion tools for DBC<->SQL, it's just a matter of "effort".
SQL conversion is useful to avoid using of client data on server (you can totally overwrite them if you don't want to go against EULA) or just extends/customize them.
Here you are the issue about DBC->SQL conversion: https://github.com/azerothcore/azerothcore-wotlk/issues/584
Grakn is awesome, but it also seems very unstable.
The exactly same initial import queries -run in another keyspace- (meaning both were empty before) are only working in one keyframe, the other throws this stupid error:
Error status: 400, error info: facebookCategory doesn't have an 'isa', a 'sub' or an 'id'
In my scheme facebookCategory is defined like this facebookCategory sub category. Category is defined as category is-abstract sub entity.
So - what's wrong with Grakn?
This is a known issue we are working on right now:
when you start migrating data on a keyspace and for some reason your schema or data are wrong/missing, the keyspace sometimes gets corrupted. So when you will try to reload data - even if now everything is correct - you will get that error, again because the keyspace is corrupted.
We are working on this issue internally to solve it as soon as possible.
The error you get is trying to tell you that there is a corrupted schema, we will try to improve it and make it more explicit so that you don't think it's stupid.
We know Grakn is still far from perfect but we can assure you we are just trying to fix as many bugs as possible.
Please try to migrate everything in a clean keyspace, you can find also more issues discussed in our github repo and our support forum
I have executed successfully - at least I could not detect any error messages - all the commands that were prompted in a tutorial I'm following, but when I try and test it on the browser, I can only display a rough table with no stylesheets or buttons or menus whatsoever.
Incidentally, in order to troubleshoot the problem I have tried to hack the code adding manually on the address bar some actions, and when I forced frontend_dev.php/job/new, I got some form, that is encouraging.
Of course there must be something wrong but I can't work it out apparently; I have done the same procedure several times and I am starting to feel a little discouraged, can anyone please help me?
Just make command
$ php symfony plugin:publish-assets
p.s don't waste your time on symfony 1.4, try learn symfony2 ;-)
Just wondering if any one might now how to fix this issue.
Every part of the databroker is created and also all the database connectivity is functional.
But once we try to place them together we come up with a error saying cannot create Null Databroker.
The thing that is really strange is that we have databrokers that are basicly the exact same working.
Can any one shine some light on this issue?
We worked on this together today. We did three things to troubleshoot and fix the problem:
we changed the calling workflow so that the dataset is refreshed inside the show-screen tags (previously, this was done before the screen was called).
we refreshed the dataset (a H2 db) and connected the database (before, it showed as pool not open)
we changed the database name to main
It is working now.
"Null databroker" suggests that the broker was not created correctly, although it doesn't look like that was the case since you don't mention having to modify it to get it to work.
In these cases it can be useful to look at the error logs through the admin app to see if there are errors being thrown at some time other than compile time.