I'm using react starter version of broadleafcommerce. (version 5.2 )
Question 1:
I added a new Category in Admin and added it to menu as well. I have changed the solr.repeat.interval option in runtime properties to 3 sec in both api, core modules. yet I do not see any new updates in the api response or in the UI.
Am I missing something ?
Question 2:
I dont know how to modify admin UI . I dont see any source code for it. Can you please answers these both ?
There is database-level caching happening, you will not see your changes immediately on the frontend unless you manually expire the ehcache cache, or wait for it to expire.
You can also disable all of the database caching, see the Broadleaf docs for more information.
Related
I have done below via APIs.
Creating the knowledge base
Adding a document to knowledge Base.
Problem I am facing is once job is done via APIs,
Problem 1:
Its not enabling the knowledge base, I have to goto dialogFlow dashboard and enable it manually
Problem 2:
Also I have to add response $knowledge.answer[1] manually too.
Question:
Can we do this both programatically. so that there is no need to goto dialogFlow dashboard screen and do this manually. :(
What I think above APIs are useless without these both options.
Note: I can paste the code if some one needs. Thank you in Advance
'KnowledgeBases' can only be Enable/Disable through UI, it's an one time configure. If that's not applicable, you can set the knowledge bases for each requests as in 2.
'KnowledgeBases' in 'DetectIntent' requests can be set through the knowledge_base_names[] query parameter.
Note that:
'KnowledgeBases' are just repositories of documents that you can use in 'DetectIntent', agent assist, etc. They don't have enabled/disabled state.
What's referenced to as "Enabled/Disabled" in the UI is an agent setting that means 'DetectIntent' uses the 'KnowledgeBases' by default if no knowledge bases are set in the 'DetectIntent request'.
Regarding your comment "What I think above APIs are useless without these both options." I think it's a valid feature request that I highly recommend for you to submit it through Issue Tracker.
We have a production app using the Instagram API - currently with only the basic permission scope approved. A couple of months down the line, we are now adding further functionality which requires the public_content permission. During development, I have used a new Sandbox Client ID, but now I'd like to have the current Live app submitted to request the public_content permission so that I can make the new functionality available to it. The Sandbox mode documentation states:
If you need access to more permissions, you can submit for review again and you will not lose access to the permissions that you have already been granted.
My question is: How can I submit a request for more permissions from Instagram when the Client is already out of Sandbox Mode?
The fact that it is already out of Sandbox Mode (with basic permissions), means that I cannot demonstrate the new functionality - after all, already being Live means I cannot authorise public_content from users. Instagram state We only review final and production version apps. Submissions with test and development version apps will not be approved. I don't see how this can be achieved?
I'm assuming that in this scenario, Instagram either does not expect you to have the functionality live (and perhaps a description/video will suffice for the extra permissions). Either that or they expect you to submit a new Sandbox app which demonstrates the functionality - but then this clearly won't be a production app. I'm clearly missing something, and the lack of documentation on this from Instagram isn't helping.
Would appreciate the help!
Just use the same process you used before. Click the "Manage" button for your client then, click "Start Submission" button under the "Permissions" tab. You'll need a new video demoing the permissions you want. This means, you need to set up the Sandbox so you actually can demo your use case for the permissions you want (fun stuff! lol).
Protip: Save your submission to a Word document so you can amend it. I made the mistake of not saving my original submission so when I went back, I had to work hard to make sure my language was in compliance with the use cases and stuff.
It's pretty simple to do what you want to do since you've already gotten through the approval process once - getting the sandbox set up can be tricky unless you have friend who will accept your sandbox invites (feel free to invite me #mikeghen, I'll accept).
If you're getting rejected, reread the use case you're applying for, make sure you actually can get the permissions you want using that use case, and then reread your document with the submission you submitted, you probably aren't being clear (Protip: don't say too much, be concise and let the video do the talking). I kind of feel silly for asking a similar question: Adding Features to Approve Instagram Client
Again, setting up a new Sandbox is probably where your struggling.
Protip: I suggest making another client (so you have a dev and production client) and then get the permissions you need using the dev client. Once you get the permissions you need, dev becomes production and production becomes dev.
Thank you for highlighting that line in the Sandbox docs, I didn't see that before. But I think that answers my question.
There's no recent posts or activity, the documentation is ancient, and my efforts to add subscription payments just outputs this for a subscription purchase:
The query calls all seem to work, the payment box opens, but I'm thinking that maybe I'm chasing a deprecated API? I'm not sure what's still active and what's not. :( I've tried in both debug mode and with a published (unlisted) app.
You may check on this link. Maybe your Google Account had Google Payments disabled for all users. Try enabling it and see if it works. You can also try deleting your card from your account and add it back again or try different browsers and delete caches.
This issue was also reported in this thread and suggested action is to contact the support team to fix the issue.
This comment mentions a partial roll out in Chrome Web Store. Where can I find that feature? My extension has more than 8,000 users but I don't see any partial roll out feature and I'm afraid to send the next version to all users at the same time.
I don't think it's documented anywhere. And I was wrong!
Documentation link: Control how fast your app reaches users.
In CWS lingo this is called "Controlled Rollout".
If you don’t see the max deploy percentage control, it may be because of the following:
You have less than 10,000 users. Currently the “controlled rollout” feature is only available for items with at least 10,000 users.
You need to upload a newer (higher) version of a package to use the “controlled rollout” feature. We can’t apply a controlled rollout to an already published package, because it may have already reached 100% of users.
It should show on the Edit page after you upload a new version that's not published yet. Here's a mention of it and how it should look:
Also, I've never actually tried using it.
Update: In the new Webstore Dashboard it's called "Partial Rollout" and has the same 10k users requirement.
I have a plugin that is triggered every time when an account entity is updated. I also have a workflow that updates the account when an opportunity is closed as won.
Plugin works well when I'm in the account form and hit the save button. Workflow works well too except that when it's updating the account my plugin is not triggered even when it should be(?).
Any ideas?
I faced a similar kind of situation as yours, where I had a depth checking enabled in the plugin code. Workflows updating the entity has a depth of 3, which will get bypassed if you have that checking of 1 inside the plugin code.
Not sure if you have a similar issue here, since you're saying it's managed code and you dont have access to it. Is it some kind of package that you bought/downloaded; or will it be possible to get your hands on the code?
You should also check if the plug-in is triggered for specific attributes. If so ensure the your wf also updates these attributes so the plug-in is triggered.
Also, the code might be targeting caller origin and denying access from async service. you need to pick under the hood to gain better insight.