When setting up a basic A/B test on a component using page editor, I received error with the following appearing in the log:
Exception: System.InvalidOperationException
Message: Test item is not in workflow
Source: Sitecore.Analytics
at Sitecore.Analytics.Data.Items.TestDefinitionItem.Start()
at Sitecore.Shell.Applications.WebEdit.Commands.Testing.StartTest.Run(ClientPipelineArgs args)
Attempting to start test created a Multivariate Test Definition Item with empty workflow section in the Test Lab
I'm thinking that those Workflow fields should have been appropriately set when using the UI on the page editor to create and start the test.
I guess I'll try reflector to find that error message in the binaries and keep digging.
Sitecore Version: 6.5.0 (rev. 120706)
I realize this is an old question, but I just encountered the same thing in 8.1 update 3. In my case it was because the workflow associated with testing (Analytics Testing Workflow, unless you've made your own) had been deleted on my local installation. Restoring it from one of our other servers made the error go away.
In Sitecore 8.1 and above there is a setting which can be turned on to allow the content authors to start test via experience editor.
Please add the below settings either as patch config file or
You can edit the value in the config file (Sitecore.ContentTesting.config).
Setting name is “ContentTesting.AlwaysShowTestCandidateNotification”
Related
Do anyone have the similar problem to control Android apps (from google codelab - fitness app) with their voice, using Google Assistant?
In my app, I tried to activate widget using google assistant (app action tool test), but google assistant doesn't give any respond. Therefore, I used the example code google gave to run, but it still has similar problem that widget isn't invoked when I use app action tool test to test the app.
Sample code google provided:
https://github.com/actions-on-google/appactions-fitness-kotlin.git
the shortcut looks like below and how :
enter image description here
Update:
After updating the new running record, the app won't respond when I want to trigger widget after the first time I can do it successfully. Do anyone have similar question or know how to solve it?
App updates running record
The widget cannot update/display the new running record
widget cannot be trigger to get new running record
I'm assuming you're talking about the codelab titled Integrate Android Widgets with Google Assistant.
I've been able to get this codelab to work - mostly.
When testing using the App Actions test tool:
Make sure you have uploaded the app to a project in the Google Play Console. You'll only need to do this once, even if you change your code.
Make sure the account you're using for Android Studio, Play Console, and Google Assistant on your device are all the same.
Make sure you've compiled the app and deployed it to your device. The easiest way to do this just to run it from Android Studio the first time.
When you create the preview, set the name and Locale.
Even tho these are listed as "optional", these make it easier to debug.
The App name should be something you know will be recognized by voice and not used by any other app. I tend to use things like "Splat" and "Bogus".
Set the locale to en-US
Click "Create Preview"
Once the preview is created, you can test the widget running by
Setting the Intent to GET_EXERCISE_OBSERVATION
Changing the value in the "name" property to something like "run". ("Climbing" will also work, but tell you that you don't have that activity logged.)
Making sure the target device is the one you're testing on.
Clicking Run App Action
And you should see the widget appear in the Assistant on the device.
You don't need to use the test tool, however. Once you have created the preview with the Test Tool, you can just test it right on the device:
Start the Assistant by long-pressing on the home button.
Saying or typing a request such as "How far have I run with Bogus" ("Bogus" being the name I've chosen this time
If you have issues with the emulator, there are some other troubleshooting steps which may be useful depending on the error message you get.
Now, I did say "mostly". I have seen issues where it will stop responding at all, either via the Test Tool or directly via the Assistant. A few things that I've done that often (but not always) help:
Delete and then create the preview again.
Remember that the Preview is only available for a few hours.
Force stop the application.
Force stop the Google Assistant.
Even if you don't see a message, check out the Troubleshooting steps for "Sorry, I couldn't find that"
from CDAP documentation exists an HTTPS post-run plugin to trigger pipeline start based on the successful execution of another pipeline (Scheduling). I'm trying to use this functionality in GCP Data Fusion but the plugin even if installed (because I can see it from Control Center) seems to be not available.
I also tried to install manually the plugin HTTP Plugin v2.2.0 as stated in the documentation but has only sink and source action. Also if I try to use the plugin an error is displayed
HTTP Properties 1.2.0 (No widgets JSON found for the plugin. Please check the documentation on how to add.)
this error seems related to the fact that Data Fusion is trying to use version 1.2.0 (the one already installed) with properties of version 2.2.0.
Any suggestions on how to solve this issue?
Update
I can see the two vesions http-plugin from Control Center
but I cannot set the version
Problem about http plugin hasn't been solved but I found the existence of pipeline trigger to execute pipeline based on status of another pipeline, this feateure is only available with Enterprise edition.
I believe you can find HTTPCallback post action plugin for the particular batch pipeline attaching appropriate pipeline alert.
Following Configure menu from the main dashboard plate:
Create the new Alert object invoking HTTPCallback plugin properties list:
Depending on the version of the you Data Fusion instance, it may still be defaulting to the old version of the plugin. To select the new version of the plugin you should:
Navigate to the Studio
Hover your mouse over the HTTP plugin in the sidebar
After a second or so, a box will appear with the plugin details. You will see the current version of the plugin and a button beside it that says "Change", click on this button. If you don't see this button that means you only have one version of the plugin in your instance.
You will see a list of all the versions of the plugin in this instance, select the one you want. The version you select will be the new default version.
You should now be able to use v2.2.0 of the plugin.
I'm trying to open my newly installed Postman when an error occurs which says something like this:
**Could not open Postman**
Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded succesfully after `dexie.open`.
Please try restarting the app. If the issue persists, please refer to http://go.pstmn.io/troubleshoot-could-not-open
As it says, the error really persists. The website above only provides suggestions like "reinstall the app" "upgrade the app", which are not really helpful. And as I dig into the Internet, it occurs to me that such error hardly happens (found nobody have the same question like me).
"IndexedDb" was mentioned in the error message, and I just know (from the Internet) that it's a nosql database provided by explorer. Maybe the problem can be solved by reinstalling the database, I guess?
I had a similar problem and found this description: https://github.com/postmanlabs/postman-app-support/issues/4897
Short answer is, delete the Postman configs directory at ~/.config/Postman (for Linux) and then try running again. This will delete any saved Postman data you have, but for a newly-installed instance that's not an issue.
Go to installation folder of Postman:
C:\Users\Davoud\AppData\Local\Postman
delete the older version's folder. It fixed my problem. Actually I also deleted update.exe too.
Can you try just by deleting the “Postman” folder or renaming it to “Postman.old” from below two locations and then reinstall the latest version from here and see if that helps?
C:\Users\<user>\AppData\Local and C:\Users\<user>\AppData\Roaming
I tried it as I was facing the same issue and, it solved for me.
Use this: It worked for me.
pkill -fi Postman
For Windows 10 - in my case, I have to:
Open Task Manager and kill/end the Postman application.
Go to %appdata% and search the "Postman" folder.
Inside "Postman" folder, select the "Postman_Config" folder1. Delete it.
Try to open your Postman instance again.
1 The "Postman_Config" folder contained (in my case) another folder called "0" and inside this folder, an "userconfigs.json" file - which only contained these characters:
{}
If you have additional information,please, make a copy of these files in order to have a backup - if needed.
For Windows -
Kill the process that says, postman from the task manager
Run the installer again, it resolved the issue for me.
disable hardware acceleration in the Postman menu in macOS, or the Help menu in Windows or Linux.
I had a similar problem installing Postman when I was on a VPN (on Windows). It started up but then got a popup error saying "TypeError: Cannot read property 'id' of undefined," and a blank white screen afterwards. So I uninstalled it, deleted any Postman folders, turned off the VPN, and re-installed it with no problems! After it installed successfully, I was able to turn on my VPN and had no further issues.
For reference, I had these errors in my C:\Users\<user>\AppData\Roaming\Postman\logs\renderer-requester.log file
[20076][1645655031650][requester][info]["Migrations: Committing IndexedDB upgrade"]
[20076][1645655031665][requester][error]["Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031673][requester][error]["Migration: Could not complete migration.",{"name":"Error","message":"Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.","stack":"Error: Migration: IndexedDB schema migration failed. IndexedDb was not upgraded successfully after `dexie.open`.\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1448541\n at file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:3000934\n at Ve (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996146)\n at ze (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2996903)\n at IDBOpenDBRequest.<anonymous> (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:2:2997272)"},{"0000_initial":"started","0001_add_archived_resources_table":"started","0002_add_variable_sessions_table":"started","0003_add_editor_tables":"started"}]
[20076][1645655031676][requester][info]["booted - requester"]
[20076][1645655031686][requester][error]["Could not complete migration.",{"name":"TypeError","message":"Cannot read property 'id' of undefined","stack":"TypeError: Cannot read property 'id' of undefined\n at t.default (file:///C:/Users/<user>/AppData/Local/Postman/app-9.13.0/resources/app.asar/js/scratchpad/scratchpad.js:477:1193039)\n at
......
bundle exec cucumber features/products.feature
Using this command I am running my cucumber test for product feature
for all scenario but it throws an error after one scenario executes
Given I am an authenticated user #features/step_definitions/login.rb:37
stale element reference: element is not attached to the page document
(Session info: chrome=46.0.2490.80)
(Driver info: chromedriver=2.13.307650 (feffe1dd547ee7b5c16d38784cd0cd679dfd7850),platform=Mac OS X 10.8.5 x86_64) (Selenium::WebDriver::Error::StaleElementReferenceError)
for authentication. But if I run one by one scenario it succeeds. Please any help how to run all scenario at time with exception.
This error comes if you look for an element on the page which is not loaded yet or expires because the dom has changed in the previous step. Make sure that when you run the your test cases as bulk each cases should be isolated from others. You should check that the element you want to interact is on the page if not add extra steps to make sure it loads there.
I'm trying to install some packages on Sitecore 6.2 solution. I'm receiving a strange packager error:
“Package generation failed: Root element is missing" . I checked logs and nothing appear.
Sitecore’s packager wasn't able to generate a package.
It appears that in the process of generating the zip, it needs to access the temp folder during the creating process.
I meet this error few times and it doesn't work allways to give access just for AppPoolIdentity.If it's not working give access for role Everyone.
Here you find a nice article about this error .
I think a probable reason for this failure could be that you created package of an item or a number of items, but its template might be missing.
Alternatively, please check that your AppPoolIdentity, (ideally Network Service, to check AppPoolIdentity Name, goto IIS Manager, Application Pools and select the AppPool of your website, and in Action Pane on right side, say Advanced Settings, you will be able to see the Name of Process Model -> Identity) has read-write rights on C:\Windows\Temp directory.
Do let me know after trying the above two things on your solution
Hope this helps!
Regards,
Varun Shringarpure