[4.1.0] undefined function Backpack\Generators\Console\Commands\str_plural() about generators HOT 12 CLOSED

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication channels:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;
• Showing off something you've made, asking for opinion on Backpack/Laravel matters - Reddit;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

--
Justin Case
The Backpack Robot

from generators.

sorry, my mistake. laravel/helpers was missing :-(. You can close it

from generators.

Actually that makes it an error @mikiman2028 - thanks for raising the issue. Our bad!

We've removed laravel/helpers in 4.1, we should account for that in backpack/generators too. I'll move this issue there to make sure we fix it before launch - thanks again.

Cheers!

from generators.

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication mediums:

• Bug Reports, Feature Requests - Github Issues (here);
• Quick help (How do I do X) - Gitter Chatroom;
• Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

--
Justin Case
The Backpack Robot

from generators.

We've removed laravel/helpers in 4.1, we should account for that in backpack/generators too. I'll move this issue there to make sure we fix it before launch - thanks again.

What is the best workaround while this gets fixed? Should we just install laravel/helpers for now?

TIA

from generators.

Hi @anovelexperience . It's been fixed in #68 , but that will only get merged once 4.1 is launched. Until then please change your composer.json to require "backpack/generators": "^3.0|4.1.x-dev as 3.0.0", - that should do it for you.

Closing the issue since it's fixed on that branch, which will get merged soon enough.

from generators.

Thanks @tabacitu. Will changing my composer cause me to lose any changes I've already made to crudcontollers or layout files (vendor/backpack…)? I'm struggling to understand the use of the pipe symbol here.

from generators.

Depends on the one you're talking about:

• It will NOT affect any changes to resources/views/vendor/backpack/...
• It will YES erase all changes to vendor/backpack/crud/src/resources/views/...

The first one is the only good way to change blade files in Backpack.

Files in the vendor folder that's at the same level as your app folder should never be changed, because your changes will be lost upon composer update. And will also be ignored by composer. Sorry if I'm dumbing it down too much - you might already know that, but many people ignore this so I felt like it needed to be said.

If you have any changes in the main vendor folder, you can just copy-paste the changed blade files in the corresponding folder in resources/views/vendor/backpack - Backpack checks there first for blade files, and loads it from there if it exists.

from generators.

That's what I imagined. I was wondering what the pipe symbol (|) meant in the composer configuration. I've never seen that before. TIA

from generators.

Or - "^3.0|4.1.x-dev as 3.0.0" reads as ^3.0 or 4.1.x-dev as 3.0.0

from generators.

Right, ok. I understand the pipe is analogous to "or" but, does that mean use what's on the 3.0 branch unless there is a 4.1.x-dev branch, in which case use that? Don't worry about answering quickly… This is just for my personal learning. I could also read the documentation!

from generators.

Well the 3.0 version doesn't exist yet. But it will once it's launched. So now it should fall back to the second option, the 4.1 branch. But once 3.0 is released it will use the official release.

from generators.