Skip to content
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

[BUG] Add Lead Buttons Do Nothing #269

Closed
ghost opened this issue Sep 22, 2021 · 22 comments
Closed

[BUG] Add Lead Buttons Do Nothing #269

ghost opened this issue Sep 22, 2021 · 22 comments

Comments

@ghost
Copy link

ghost commented Sep 22, 2021

Bug report

Kanban Add Leads Button Has No Effect

Issue Description

In the Leads package, each Kanban board has an href button that says Add Lead. Clicking them has no effect.

Preconditions

PHP 8.0.7 on Laravel Valet
Krayin v1.1.2

Steps to reproduce

Go to Leads page, see kanban board stages, click on outline button with text Add Lead.

Expected result

Clicking on the Add Lead button should ideally produce a modal to add the lead to the specific stage, or at minimum redirect to the leads/create page.

Screen Shot 2021-09-22 at 4 07 32 AM

Actual result

Nothing happens, no modal opens or redirect occurs, just an empty pointless click.

@Sanjaybhattwebkul
Copy link
Contributor

Sanjaybhattwebkul commented Sep 22, 2021

@19peaches
This issue is fixed in master. : #244
Please take a pull from master. then try again.
If you will get the same issue then let me know

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Hey Sanjay, thanks for that.

I installed with composer as per your docs, since none of this is registered as a vendor package, except the krayin/krayin-package-generator package, I have no way to pull master into my root directory.

Should I just nuke this and re-install via cloning the repo?

@Sanjaybhattwebkul
Copy link
Contributor

Sanjaybhattwebkul commented Sep 22, 2021

Yes, you should re-install via cloning the repo

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Ok thanks.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

How do I get all the javascript assets installed and compiled, do I have to go into each of the packages and run these individually or something?

@devansh-webkul
Copy link
Member

Hi @19peaches,

Are you working on the package?

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Well I'd like to, once I wrap my head around your set up.

I certainly have some cool integrations to add that we use in our business.

For now, I need to get it running.

@devansh-webkul
Copy link
Member

devansh-webkul commented Sep 22, 2021

Well if you are working in the package then you need to compile the package individually but make sure you are aware of the updates because it's the same thing as the vendor folder.

As I recommend you to publish all the packages and override the methods which you think it's not suitable for your business.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

I'm trying to do an initial install.

I cloned the repo per Sanjay's instruction.

Ran composer install, created an app key, ran krayin:install ran npm install and npm run dev

I have no node_modules folder and no assets compiled.

@devansh-webkul
Copy link
Member

After krayin install no need for any assets compiled because we already delivered compiled assets and it's already published during installation.

If you run npm install and npm run dev that is your project environment which is in the root.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Well after krayin:install I get this:

Screen Shot 2021-09-22 at 6 16 47 AM

@ghost
Copy link
Author

ghost commented Sep 22, 2021

And before you ask, there were no errors from the installer when I ran it.

@devansh-webkul
Copy link
Member

Just run php artisan vendor:publish --all --force.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Ok that worked.

Now when I want to make some changes to js or scss in a given package, what are the steps to follow to republish?

@devansh-webkul
Copy link
Member

  • Go to a specific package.
  • Run npm install.
  • Run npm run dev or npm run watch as per your requirement. Once you are done with your development.
  • Run npm run prod.
  • Run php artisan vendor:publish --all --force or specific package you want.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Great thanks.

I just noticed that now, the lead stages are all chopped off from the way they were.

Screen Shot 2021-09-22 at 6 33 21 AM

@devansh-webkul
Copy link
Member

This has been fixed recently. Just run git pull, if you have taken clone.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Will do.

One last question, how can I build on the core packages when any pull will overwrite my changes?

@devansh-webkul
Copy link
Member

Well if you are working in the package then you need to compile the package individually but make sure you are aware of the updates because it's the same thing as the vendor folder.

As I recommend you to publish all the packages and override the methods which you think it's not suitable for your business.

Well, I already told you here.

@ghost
Copy link
Author

ghost commented Sep 22, 2021

The issue with the stage being cut off is not fixed.

I have the latest code and it remains the same.

@devansh-webkul
Copy link
Member

Just wait for merging of this, take a pull,
#271

And then run,
php artisan vendor:publish --all --force

@ghost
Copy link
Author

ghost commented Sep 22, 2021

Got it. Thanks.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants