I have a masterpage that uses a js file in the layouts folder. I want to manually edit this file for development purposes, but my browser does not get the latest copy if I manually open the layouts folder and edit the file. I tried doing a hard refresh on the client-side with CTRL+F5, but I still get the old copy.
Is there an easy way to edit this file without redeploying my masterpage feature over and over again?
You don't need to redeploy it. You need to clear the browser cache. If you open it from another browser, or if you clear the browser's history, you'll see you don't need to redeploy it.
Related
We have been stuck on using Internet Explorer in my company for one single reason: when you click on a sharepoint link to a Document in IE, it opens the file as editable. So when you save it, it is automatically saved on the server.
On the other hand, with Chrome or other browsers, it downloads a copy of this file, so the user might loose changes because he thinks the file is saved on the server whereas really it is not...
Anyone thinks of a solution for that?
Thanks !
There is a similar resolved question to yours right here:
How to open SharePoint files in Chrome/Firefox
give it a shot!
I am just starting with Aptana and I don't have the original HTML files for my web site. Is there a way that I can import my whole web site as a project or do I have to open each page from with Aptana and save with the original urls?
Thanks
I use Interachy which is a commercial Mac option. One open source Windows program is HTTrack.
If your site isn't large, it's often feasible to go through page by page and save each one as source. You also need to save all the images and CSS files, and reconstruct the folder directories, though it's goes faster than you might think.
Good luck!
I have content editor on my team site where I added several links. But today while adding some new links, content editor crashed. so now when I tried to open site containing content editor, browser stop working.
The quick solution is:
I can delete the existing content editor and create a new one (using ?contents=1 in the corrupted team site). But since my content editor contains lot of links, so is there a way where I can roll back content editor to previous version (till yesterday afternoon)?
Any suggestion is appreciated.
Your previous version is probably lost in the mess. You will have to go to the site admin, and close / delete the webpart and start over. You may be able to simply close the web part (from site admin) and then edit the web part properties to salvage it's contents.
Either way, content should not be added directly into a Content Editor Web Part (for this reason.) Instead, use the option to point to a file in a Document Library elsewhere in your SharePoint site, with versioning enabled.
Then, in the case of the CEWP blowing up the page from an edit to the contents, you can revert to the previous version of the document, and the CEWP will immediately be updated, and the page immediately restored.
Stackoverflow is about programming related questions, your question is more of a user question.
You can't roll back a content editor. If you have versioning enabled for the page you have the content editor on, you might be lucky and can retrieve an earlier version. Otherwise you could only check the database for the content editor contents, but that will be a pretty tedious task finding it.
I am working on an intranet in Sharepoint online. I have added a custom css file and included it in the masterpage, after the default stylesheets. In the sourcecode I can see it clearly and I can follow the path to its intended file.
Earlier I had no problems to check it out, edit in Sharepoint designer, save it, then checking it in and changes would apply to the site.
But now the changes I make don't seem to catch. I have cleared cache on several browsers but still no change.
The masterpage and the custom startpage are both published. No files are left checked out.
I may be a sharepoint noob, I have searched any number of forums but not found anything pertinent to my problem.
Can anyone give me a pointer in the right direction please?
:)
Do you save the CSS file in a document library that uses versioning? Perhaps you forgot to publish the latest version of your changes, so browsers only see your previous version.
I made an account specifically to respond to this post because I was having the same issue and found your update about creating a new CSS file helpful in determining the real issue. So I wanted to share my solution!
In the end I discovered it was our BLOB cache being enabled that was causing the issue. We had enabled it to use image renditions. As per the following technet article regarding configuring the BLOB cache, I removed CSS from the file types and our issue was resolved!
http://technet.microsoft.com/en-US/library/cc770229(v=office.15).aspx#BLOB
I hope this helps :)
You are logged in as the Site Collection administrator?
CTRL+F5 to get the latest .css from server?
When you View Source you are able to see the link to your .css file?
When you follow the link to the .css file and open the .css file, it has the recent changes you made?
I think you might have done this.. but make sure after publishing the .css file it is approved.
Press F12 to load IE Dev Toolbar to see what styles are being used in the elements in question. May be you have a small syntax error in the recent classes you added.
Thanks, Karthik.
In the end I made a copy of the css file, gave it a new name and referred to that instead, worked like a charm.
Thanks for your answers and comments all
Under Site Collection Administration settings, go to SharePoint Designer settings and make sure all the checkboxes are marked including "Enable Customizing Master Pages and Page Layouts "
Also, make sure your tag that cites your custom CSS is just below the last meta tag in the head of your master page.
Lastly, remove quotes... there are additional quotes added with javascript so you don't need quotes AND have the full URL to the stylesheet or it will not work!
I'm making some changes to a legacy classic ASP application. I've made the changes locally, and now I want to copy the changed files to the server. At the same time, I need to download the Access database, add some fields to some tables, and upload it again. For this reason, I need to be able to stop visitors from modifying the database while this is happening.
My main question is, what is the best way to setup a quick "Down for Maintenance" page that will be shown immediately and no matter which page the visitor requests. The application is already established, so I'd rather an answer that didn't require me to rework the application's architecture.
My second question (maybe this should be a separate question):
Is there a better way to add fields to a db table than to copy it down, modify, and stick it up again? Please forgive if that's a dumb question - I'm new to ASP - new to Windows too.
I only have FTP access to the remote server.
Thanks.
two ways:
1
if you do a server-side include in every asp page you can do a response.redirect in that include to /upgrading.html
2
in global.asa you can do a response.redirect in the session on start event. THis is probably the best way. Will only work for .asp pages, not if the client comes to a .html page.
Do you have any control panel access to the site at all?
When I used to run a number of ASP Classic sites I often turned them off for the five minutes required to do what I needed.
Rude to do to your visitors I know.
As others have said you could redirect to a page, but that won't stop people visiting static content in html pages, but then that probably won't matter, at least it stops them making changes to the mdb whilst you download it.
It's a pity that ASP.net's app_offline.htm doesn't work for ASP classic.
Another option I used to use was to create a default.htm file that had the offline message, and the way IIS was setup default.htm overrode default.asp, so simply uploading default.htm changed the homepage. This of course doesn't stop anyone using any of the other .asp pages.
So no real answer! Sorry.
If you have just FTP access to the server (and no control over the IIS) just insert a response.redirect to the "down for maintenace" page in top of all the asp pages, and remove it when the update is completed.
The changes to the database can be performed with the ALTER TABLE statement.
With regards to the "Down Maintanance" page issue you can and taking mapache's idea a step further if there is an included file (for a header) in each of the pages you can put the Response.Redirect in that one file and upload that in place. This will avoid making changes to all pages.
Another option is to upload a temp html file which will be found first by IIS. In IIS you can set which page name.ext are looked for in a domain/folder. For example when you browse to www.example.com you don't specify the page you are looking for so it could load index.html or index.htm for example depending on setup. It will depend on your hosts configuration setup, but a bit of trial and error I'm sure you can find out which one they use. Common ones for IIS are default.htm, default.html, index.html and index.htm. You can then put it in each of the folders in the website (not ideal I know) and then carry out your maintenance.
When updating databases you can run a migration script, written in sql, to update the schema and data of the db. As you only have FTP access this will require some sort of page you can paste the sql into and run. This however opens security issues so downloading the db, making the changes and then uploading again is probably easier. In addition to doing it this way you can also save the file and you'll have a backup :-)
Hope this helps.
Better than an include file, just use the Global.asa.
In the Global.asa's Application_onStart, add
Application("Offline")= True
at the top of all of your ASP files, add
If VarType(Application("Offline")) = vbBoolean Then If Application("Offline") Then Response.Redirect "App_Offline.htm"
(The double-if gets around the lack of VBScript's short-circuit operators, and therefore any data type errors.)
You could even set the Global.asa code to
Set fso= Server.CreateObject("Scripting.FileSystemObject")
Application("Offline")= fso.FileExists(Server.MapPath("App_Offline.htm"))
Set fso= Nothing
Which would enable the offline page if it exists, like ASP.NET. However, the application start code is only reparsed when the server is reset (using iisreset), or when the Global.asa file is modified, merely adding the App_Offline.htm will not be enough.
Add below code in web.config
<?xml version="1.0"?>
<configuration>
<system.webServer>
<modules runAllManagedModulesForAllRequests="true" />
</system.webServer>
</configuration>
And place app_offline under root folder. This will work.