I wanted to know the limitations of Visual editor in Optimizely? I am running a A/B test and wanted to make a few visual changes in my app. Can I make these changes when my app is live ?
The only limitation I could think of would be... it wont execute javascript for you.
And the order of execution that it would be executed last, after the custom JS/CSS.
Yes you can make changes when your website is live, so long as you don't publish it wont get reflected on your website. Utilize the preview mode to making as many changes as you want.
Related
So while using "themekit" in vs code terminal, I get the following message:
"This is the live theme on my-store. If you wish to make changes to it, then you will have to pass the --allow-live flag"
and to resolve it, I add --allow-live flag to the command and it works fine.(as described in the other answer on stack overflow)
BUT, while it did resolve the issue, everytime I try to use theme watch or theme deploy, it repeatedly asks me to use the --allow-live flag.
While researching themekit on google, youtube and other tutorials, I saw that it works fine for other developers even if they don't use --allow-live.
I read the following shopify documentation as well- https://www.shopify.com/partners/blog/checksums
How is "theme watch --allow-live" different from the "theme watch" command, and how do I make sure that everytime I use themekit, it doesn't ask me to add the flag. Is there a way by which it automatically allows live changes without manually adding the flag everytime I try using themekit.
The --allow-live is used only when you are working on a live theme.
If you don't want to use the --allow-live you must create a development theme and work on that, then the flag will not be required.
Please note that this flag was added recently (a few months back) so it's possible that you are reading older documentation where this flag was not present.
The flag cannot be stopped on a live theme, this is a prevention rule so that you don't overwrite the live theme without knowing that you are working on it.
So theme watch and theme watch --allow-live do the exactly same thing, but the second one just allows for the modification on the live theme.
Very new to Google Actions. Testing out tutorial stuff.
I have tried this in a couple of test projects just to double check. After initial run of any project I do not get any updates on draft projects. No changes show up in draft projects for me for both simulator and real device.
Started new project
Even blank project has basic conversation telling you where to add things next.
Change text.
Notice prompt does not change in testing environment.
In below pictures I have changed the words "hello world" with "Hey Dude" for both fulfillment and console output. I would expect Testing Prompt to respond with "Hey Dude from fulfillment and Hey Dude from the console!" But it does not. Instead it does not reflect any recent changes.
I think there may be two slightly different (but sometimes related) issues going on here.
The first is that there are known problems with the simulator being slow to pick up on updates, or them not seeming to show up. The second has to do with making sure you're deploying changes from the build-in code editor.
I don't have a clear answer to the first problem, although I know they're looking into it. I find that I can make some changes and they may not be noticed, but I know they have been picked up if I see the "Your preview is being updated..." spinner appear. There are other spinners that sometimes appear, but unless it explicitly says that it is being updated - the updates aren't always picked up. (Sometimes they are, however.)
Usually, if I don't see this, I'll go back and force an apparent change (delete a character from a webhook handler name, then add it back) and go back to the simulator. In general, this time it will say it is updating.
If you're using the Cloud Functions editor, you need to do three things:
Save the changes. You'll do this by clicking the "Save Fulfillment" button, but this only saves it so you can leave the editor. It doesn't mean that the simulator has access to it yet.
Deploy the changes. This deploys your code to Cloud Functions so they can be run. Note in the illustration that it says the code is saved, but not yet deployed.
Wait till the changes are fully deployed. Deploying takes time, and until it is completed, it won't be available in the simulator. While deploying, it lets you know.
Once it has deployed, however, the message changes, and you the impacts should be available through the simulator (although you may still need to see the "being updated" message to be sure).
Remember, however, that you don't need to use the "Cloud Functions editor" in order to deploy a webhook. You can deploy a webhook on any web server where
The host is public (so has a public IP address that Google can reach)
It can handle HTTPS with a non-self-signed certificate
You can even deploy yourself to Cloud Functions for Firebase, which is the same service that the Actions Builder uses. This way you have the URL set once in the Actions Builder and, once it is set, you won't need to change it.
But you'll still be able to change your code by managing your own deployment separate from Actions Builder.
I can't seem to find any information on whether a ReliableCollection, specifically ReliableQueue is persisted between debugging sessions in visual studio. It does not seem like it is. I think it's because the application is removed and then re-added during debugging. Can anyone confirm this?
Yes, the default behavior is to remove the deployed application after the debugger stops.
Fortunately, you can change this.
There are two ways this can be done: Launch your app from VS without
the debugger attached (Debug -> Start Without Debugging [Ctrl+F5]).
Obviously, this would require you to manually attach VS to your
service processes in order to debug them. When you detach VS from the
processes, VS will not remove the application in this scenario.
With
your Application (.sfproj) project selected in Solution Explorer, go
to the Properties window and change Application Debug Mode from
"Remove" to "Auto Upgrade". This prevents VS from removing the
application after debugging. However, it also causes another change in
behavior in that it will automatically upgrade your application each
time you launch it from VS. The added benefit of auto upgrade is that
your application state will be maintained across multiple launches
from VS. This may be desired or not. There is not a setting that
allows you to both prevent application removal and not do an auto
upgrade.
Assume that I have two monitors assigned to my pc. Now I want to get the preview of a web site while coding it. Is there anyway to do this?
eg:- Do the coding from sublime text from a one monitor and the meantime watch the output from the Firefox web browser.
I have used live.js for this more than once. It can work either as a bookmarklet or embedded on your page, and it works in any browser as it's not an extension. Also requires no other software to work.
The downside is it that it will flood your developer tools with HEAD requests every second or so to determine when to reload things. That's the cost of not having to install external software.
You can use the LiveReload plugin for SublimeText. It listens for changes to your code files and updates them in the browser in real time.
Also, do not forget to add the respective browser extension. That should save you from adding any scripts into your page.
You could use yeoman ( with Grunt or Gulp depends on which generator you want to use ).
I'm using Google Chrome Developers tool and console while developing and debugging my web applications.
I've some Chrome plugins/extensions installed. These plugins/extensions add extra markups and scripts in the pages while rendering them in the browser, and when I view my codes in the developers tool, makes it a lot messy.
I want a clean way to view my codes without those extra markups.
So is there a way to toggle (disable/enable) the plugins quickly, or in the best way, to disable them in a particular tab? I've several plugins/extensions installed and I don't think it's a good idea to disable and then re-enable them manually.
Besides, I may want to use a plugin/extension while I'm browsing other websites on other tabs simultaneously.
There's no mechanism to disable an extension for a specific tab, or specific host. You could hack something together via the management API that would disable extensions when you hit a specific URL, but that disabled state would be global, not local.
Extensions don't, however, run in Incognito mode (unless you explicitly whitelist them via a checkbox at chrome://extensions): that might be a decent workaround for you. Load your in-development site in Incognito, work with it there in a clean environment, and pop back into your regular window for normal browsing.
You could, of course, accomplish the same thing by setting up a specific profile for development in which you simply didn't install extensions.
These are workarounds, of course. You should feel free to file a feature request for more granular user-side control over when extensions are loaded: http://new.crbug.com/
Would running 2 separate instances of Chrome be of help for you?
(You can start 2 unrelated Chrome browser instances from a command line specifying different user directories: chrome --user-data-dir=userdata1 & chrome --user-data-dir=userdata2 )
I haven't tried it for your usecase, but it sounds reasonable.