Well, the title says it all really, I am just wondering if I can do changes in Studio that won't go live immediately for public. Like fine tuning with settings or even adding new apps.
Could you please specify which changes do you want to "hold on"? If you mean the template looks then some templates (like Lucid or Protean) have the mixes which can be shown only after the publishing.
It is literally all changes that take place in studio. Any time a content module is added, a link to it immediately goes live on multiple menus. If you are building on a page and a raw block is added, it is immediately added to a page and you have to change it very quickly so people don't see it, etc., etc.
There is no building behind the scenes, being able to preview it and then publish it to the live site. Everything is done in real time.
This is the way how the Web works - the HTML / CSS / PHP / Javascript changes make the instant effect. The only quite safe way for that - just have the copy of the site in the subfolder and make the changes there first.
as dear @LeonidS described, I'm using a test copy of our site for bug hunting of newest Alpha and Beta versions as well as for testing new modules, before finally implementing them on our live/production site. When installing a second copy of the UNA framework in a subfolder of the root of your main site installation, one can share one single license for both installations as a Premium UNA member.
This approach not only gives us the guarantee that the UNA framework runs flawlessly on our server, but also the opportunity to test changes until they are ready to be released for public use on our live server.
At the moment, the current version 14.0.0-RC1 is running on our test server and version 13.0.0 is running stable on our live server. Our next live server update will probably be version 14.0.0-Final.
The only disadvantage of using an installation in the subfolder in the root of the live server is that you can no longer log in and out of the test server if you are logged in to the live server at the same time. Somehow the two installations seem to share the same login data.
Hello @David Pinter !
Could you please specify which changes do you want to "hold on"? If you mean the template looks then some templates (like Lucid or Protean) have the mixes which can be shown only after the publishing.
It is literally all changes that take place in studio. Any time a content module is added, a link to it immediately goes live on multiple menus. If you are building on a page and a raw block is added, it is immediately added to a page and you have to change it very quickly so people don't see it, etc., etc.
There is no building behind the scenes, being able to preview it and then publish it to the live site. Everything is done in real time.
Hello @Corey Dozier !
This is the way how the Web works - the HTML / CSS / PHP / Javascript changes make the instant effect. The only quite safe way for that - just have the copy of the site in the subfolder and make the changes there first.
D
Thank you @LeonidS, that sounds like a fair solution!
So, just to clarify, if I want to make an unpublished change:
Is that correct? If yes, I still have some questions:
Thanks for your help!!
Yes, almost the completed way except:
1) The subfolder UNA is better to connect to the separate database too.
2) Instead of direct copying, it is better to repeat the successful actions in the main site.
Yes, the key-secret pair works in one domain, so the mods should work in the subfolder too.
T
Hi folks,
as dear @LeonidS described, I'm using a test copy of our site for bug hunting of newest Alpha and Beta versions as well as for testing new modules, before finally implementing them on our live/production site. When installing a second copy of the UNA framework in a subfolder of the root of your main site installation, one can share one single license for both installations as a Premium UNA member.
This approach not only gives us the guarantee that the UNA framework runs flawlessly on our server, but also the opportunity to test changes until they are ready to be released for public use on our live server.
At the moment, the current version 14.0.0-RC1 is running on our test server and version 13.0.0 is running stable on our live server. Our next live server update will probably be version 14.0.0-Final.
The only disadvantage of using an installation in the subfolder in the root of the live server is that you can no longer log in and out of the test server if you are logged in to the live server at the same time. Somehow the two installations seem to share the same login data.