So I'm tinkering with using Umbraco as a CMS for an MVC application. Of course, I run the site locally and publish to a server and use Umbraco for managing things like hero images, carousel text, and a few basic dynamic elements that are stored in Umbraco.
However, one can also modify the actual template .cshtml files as well through the Umbraco back office. The problem with that is that those changes won't be reflected locally, and any changes made in the Umbraco back office would get overwritten on the next publish.
Is there any way to 'pull' the changes made in Umbraco (without having to FTP in and download the entire site), or even better integrate it with git directly?
If I understood you correctly, Umbraco uSync package might help you:
https://our.umbraco.org/projects/developer-tools/usync/
It exports the changes in "uSync" folder locally - you can do this automatically or manually, and then you transfer those files on the server, and do import within Umbraco Dev section.
Yes use uSync for this but you should probably decide whether you edit your template files locally or on the server. Generally you would probably keep editing template files, CSS, js, locally and upload changes to your live site. However, if you are adding content, setting up a template for the first time, changing doc types, adding data types etc, these are all database changes so either; share the database on the server between your local and Server versions of the site; or use a tool like Courier or USync to replicate your changes between environments.
Related
I'm unable to get server side includes (*.html files) working in a .net core razor pages web application. I've made sure to have the appropriate handler in my applicationhost.config, but I'm thinking there's a different issue here. Any help is appreciated.
Why am I doing this? I have multiple web applications sharing the server side include files (for navigation bar, footer, head content, etc..). Each of these different applications may be of different Microsoft web architecture. Our goal is to move everything to .net core, but we have lingering web forms projects to deal with along the way.
I have performed a work around by taking the SSI file contents and using #Html.Raw to serve up the content. This is probably wrong also.
I went ahead and changed the file extension of the html files into cshtml which allowed me to treat these files as partial views. I'm using a prebuild event to copy these files from a shared solution folder into my project Pages/Shared/ssi folder. I also copy those partials into wwwroot/ssi for the other applications to use via SSI. Eventually all of the apps will use the partial views instead.
The problem with this solution is that it is not necessarily clear that all edits need to happen in the shared solution folder instead of directly in the project, but the documentation for the project will address this. I tried using linked files, but only one link to a specific file can be made in a project.
Not a perfect solution (to the problem), but this not a perfect website either.
I'm facing some problems, somehow to provide to content authors solution/advice to delete huge sections of website translated (having language versions) and with references set on presentation or data items inside content tree.
Removing all items plus references raise another problem how to make the changes visible on web database. Publish cannot be used, even workflow is present changes are made on presentation (master instance is mapped to a preview site for client) on pages (by different agencies) and cannot reach live, only when they decide to. Used as well number of versions per language (limited to 6, rest removed) if all 6 variants are trapped in workflow publish will publish item with all fields empty, we don't want to have a blank page.
And there are other concerns regards incorrect work, sometimes agencies publish/submit incorrect/unproved content and they blame each other case someone publish accidental pages (presentation settings/datasource) so i want to pick the best strategy here not to give room for content authoring agency's to blame their incorrect work other then them.
I have few approaches to do it right but..
do same deletion of items on web database via CMS in theory works (tested on locally in sitecore 7.2 - works) on Production CMS (Sitecore 7.0 - admin rights, no access to server files for me) fails as in next image:
write a module (Sitecore command to remove all references and removing/recycling web database item cannot be performed via code because it will trow same error as above)
Question 1. Why this error occurs at CMS item deletion if web database is selected (Sitecore 7.0)
Found in this deprecated post something what seems to be the solution: Add publishing commands to the recycle bin. Well here I get a bit blocked, adding the publish command on Recycle Bin ribbons, don't know if it's possible to do this (what I'm publishing I do not understand). I created something but it's not working:
This is the result :(
Question 2. Is publishing commands to the recycle bin possible? If yes please help me with a documentation to implement it and understated what/how is published.
If you have other suggestions (beside publish item + sub items or publish website) please help me out.
Thank You.
Currently the webmaster can go into IIS and edit files by using Dreamweaver. The problem came when developers deployed a Web Application Project and the webmaster changed the master page to update the design, but then when developers deployed updates to the WAP it overwrote the master page back to the way it was.
So my question is, what is the best way to let the webmaster/designer edit the master page design in an ASP.NET WAP and keep project files in sync with developer projects?
Currently the webmaster can go into IIS and edit files by using
Dreamweaver
That means webmaster is actually editing the production copy of files. Don't do that. Why would you allow production copy to be modified. Rather, as already suggested by #BenRobinson; have webmaster make changes to the version already present in TFS (considering the face that, production branch is different in TFS than main code branching).
That way, once it's been approved that the modified changes are per requirement then you can copy the changes to production branch and do a full deployment along with other code changes.
I have looked for answers to this question, but I am not sure if I am asking it right.
I am looking for what do developers do in this situation:
I am developing an ASP.NET C# applications. I have CSS and SCRIPT files, and I am using jQuery. I install my application to the Web Servers (or I have my customer install them). If I have made any changes to my script files by adding some new jQuery or something, my customers don't get that effect after I do an update. I assume that the reason is that their browsers cache the file on the local computer and they do now download the new file from the server.
In my development environment I clear the cache when I close the browser and on IE I tell it in options to always load from the server. That way when developing I never have cached data.
What is the best practice to make sure that if I do make changes, those files get refreshed on the client computers after I do an update? Is there something in Code I can do?
I really don't want to change the filename and update all my script references.
Thanks,
Cory
The traditional way is to append a query string argument to the end of the reference to the css/script file path. For example, if you append a build number as the query string, each version of the software will make its own request for the relevant resource.
I have added a custom button, with url + javascript by chaning the isv xml file, as described on
http://msdn.microsoft.com/en-us/library/cc150860.aspx
and all works fine. However, when I try and replace the file in the /ISV/ folder, it behaves the same as the original copy, I assume this is caching related. However, if I access the file from outside the CRM that is http://server/ISV/file.htm it has the latest and correct version. How do I get around this caching issue.
Thanks
So your ISV Option points to "/ISV/file.htm"? I think in the past I've noticed CRM's IIS site caching static files for 3 days. What I would do is when you replace your file.htm in your ISV folder, also update the ISV.config:
So change it to point to "/ISV/file.htm?vers=00001" and then increment each time you update the file.