-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to install - mismatch between giiant's required version for yii2-gii and current verions #251
Comments
A workaround could be to require `"yiisoft/yii2-gii": "2.1.0 as 2.0.999". Could you give this a try and report back here. @samdark @cebe Is there a special reason for |
Extensions were never tied to framework versions except just after first releases. See https://github.com/yiisoft/yii2-twig/releases for example. |
But were there minor breaks? Is there something we need to consider before upgrading? |
In the gii? It's now bootstrap 4 instead of bootstrap 3 so yes, there may be issues with custom panel styling. |
@Larrytx I'd be waiting for feedback from your side, if this runs with gii 2.1 and BS4. |
@schmunk42 Sorry to take so long getting back to you. Got called off to work on another emergency. Now, back to working on this one. Help me out here because I can't seem to get this one to work. I'll start with the result I'm getting; then, I'll give you what led up to it.(I have a feeling that I've made this one more difficult than it has to be.)
By the way, I'm using
Note: Class
I'm guessing that the error may occur because I cloned the extension instead of installing through composer and didn't know what else to do afterwards. I'm wondering, if we can somehow work through all this, if the following dependencies won't create some problems:
Anyway, if you can tell me how to proceed, I'll be happy to work on it. |
You need to use |
That appears to have worked! |
By the way, you have a number of annoying dependencies that don't show up until you have created things with giiant and attempt to make use of them. With regard to the Modules Generator, you get the following:
It would be helpful if your instructions at least pointed out that you have to install these independently before making use of the files generated by giiant. Please don't automatically load these as dependencies. I absolutely hate yii's AccessBehavior and always go with RBAC. As to font-awesome, like most users nowadays, I load it as part of my asset bundle. Actually, I load Font-awesome Pro. I'll try rmrevin's rmrevin\yii\fontawesome\NpmProAssetBundle, but I'm not sure if it offers enough to make me back out of what I've got installed. |
I totally agree, these are leftovers from usage in phd, we need to clean this up.
Actually our
Yeah, font awesome should be removed, also a leftover from the early days, when we thought AssetBundles will solve any problem. 🙄 |
Actually, I have looked a dmstr's AccessBehaviorTrait multiple times. I remember it often; every time I have to comment out your usage of it. When I said RBAC, I meant real, functional RBAC, i.e., RBAC built on the standard three database tables. I only consider database-driven RBAC. |
I was able to use the Module generator successfully. However, as soon as I attempted to go the giiant Model generator, I got a fatal error that seems to derive from Gii. The trace is:
Please let me know what to do next. |
Could you double check the (POST) data which is sent by the form and how it's received on the server, somehow |
I will attempt to get you the POST data — as soon as I can get beyond the multiple, egregious problem that I've encountered by attempting to use rmrevin's fontawesome extension. This is a perfect example of why you shouldn't try to force something like this on anyone. My application, like thousands of others, is an advanced template. In my advanced template site, I've got a node_modules folder that is on the same level as the backend, frontend, and vendor folders. I cannot and never have been interested in maintaining separate node_modules installations for the backend and frontend, and in my case, my separate storage, applications. One is enough, thank you. Here's what rmrevin's extension's NpmProAssetBundle looks like:
Unfortunately, I installed this extension last night. When I pulled it up today, of course, it totally failed with the following fatal error:
So now, I'm going to have to clone his AssetBundle and rework it into something usable. But wait. I've got a backend theme that I'm using. There is no Making all these presumptions about someone else's web application is just how the developers of extensions make it totally impossible for neophyte developers to create anything in the Yii2 framework. I must admit that Revin does provide good advanced documentation for his extensions (at least those for which the documentation is available in English), but he totally misses it on the very most basic level, the very level at which the most basic of users will be tripped up, throw their hands up, and run to something else, some other framework. As for me, I guess I'll spend the next several days trying to refactor his extension into something usable. (No doubt, the lack of a webfonts directory will cause some inscrutable error that will cost me countless hours of work.) When I get that finished, I'll try to get you the POST data. This will be a neverendingsaga. |
@Larrytx Could you give this branch a try https://github.com/schmunk42/yii2-giiant/tree/feature/removed-fontawesome Lessons learned, we'll use fewer deps in the future, I also noticed there there are dev-dependencies which are actually one required for testing the generated code, which is a pretty special case. |
Tobias, some preliminary observations as I worked through this. On the Module generate/create page https://gii/default/view?id=giiant-module)(, this is what appears at the top of the page:
Same thing occurs on Model generation and CRUD generation. If you need copies of those, let me know, and I'll send them on. As you might expect, when you complete the form and submit, it returns with an even larger amount of this stuff. As to whether it works otherwise, drum roll please, it's perfect. |
Is this shown in the browser, could you post a screenshot? |
You’re right the forms/create pages all look great. Now, if I’d just follow my instincts. I started to attach screenshots before. The problem is that the text that spills out at the top pretty much takes up all of my 24” monitor. (When I scroll down, the form always looks great.) Anyway, here’s what I’ve attached:
1. Giiant Model 1: The Giiant model creation page when I first get to it, before completing the form.
2. Giiant Model Debug 1: The debug info from #1.
3. Giiant Model 2: The Giiant model creation page after completing the form and clicking Preview.
4. Giiant Model Debug 2: The debug info from #3.
5. Giiant Model 3: The Giiant model creation page after clicking Generate.
6. Giiant Model Debug 3: The debug info from #5.
Hope all that makes sense. If I can explain it any further, just let me know.
Also, I only included screenshots from Model generation. If you’d like me to do screenshots from Module and CRUD, just let me know.
Larry E. Lutz
From: Tobias Munk <[email protected]>
Sent: Friday, May 3, 2019 4:15 AM
To: schmunk42/yii2-giiant <[email protected]>
Cc: Larry E. Lutz <[email protected]>; Mention <[email protected]>
Subject: Re: [schmunk42/yii2-giiant] Unable to install - mismatch between giiant's required version for yii2-gii and current verions (#251)
this is what appears at the top of the page
Is this shown in the browser, could you post a screenshot?
Maybe some debug output in your project.
Actually The forms/create pages look good to me.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fschmunk42%2Fyii2-giiant%2Fissues%2F251%23issuecomment-489024212&data=02%7C01%7C%7C481a64c72a0f48aeda0708d6cfa7c4ec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636924716796417391&sdata=fr2vFs9F3azzRHdCsYJp1tjbLGOxdIwnGMqbxZKAyv8%3D&reserved=0>, or mute the thread<https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAAFCBZX4IZGJHUXH4KB4L3PTP675ANCNFSM4HBG2QOA&data=02%7C01%7C%7C481a64c72a0f48aeda0708d6cfa7c4ec%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636924716796427397&sdata=g%2F9e5mCBKv4OU24GDmqB9IH%2BN2o7%2FPxVl%2BP8tyxE944%3D&reserved=0>.
|
There are no screenshots attached, you might need to add them on GitHub directly. |
Could you search in your code for |
In a new installation of yii2 ver. 2.0.15 advanced-template, I am unable to install giiant. I have tried all three of these in composer.json:
All three produce this stack of messages:
It would seem that giiant requires ver. 2.0.6 of gii, and the current installation is at 2.1.0.
Is there any workaround? Any timeline for an update?
The text was updated successfully, but these errors were encountered: