When I go to edit my editor_styles in Kentico 11, I get two windows. I've never seen this before and it doesn't happen in many other instances of Kentico that I'm running. Has anyone ever seen this before?
I tried clearing the cache, restarting the site, etc
EDIT: Just had to resign all macros and now all is ok again
Three things could cause this:
Cache. Could be browser cache or server cache so be sure you've cleared ALL your cache, especially if you've recently applied an upgrade or a hotfix.
Macro signatures from an upgrade or change in your hash string salt. Be sure to resign all your macros
Upgrade/hotfix application. If you've recently upgraded or applied a hotfix, it could be a dll mismatch or some js file which was not overwritten. Check the upgrade/hotfix log file for possible issues.
Related
I'm using Firefox and use console.log quite a bit.
It just got updated to version 100, might have something to do with it.
But now files updates stop appearing in the browsers localhost upon refresh.
It's like the browser is still just seeing the older version of the files.
I have through trying and testing, found out that by going:
History
->Clear Recent History
->Select only cache, over the last 1 hour
And then click ok.
After that I can update the file and the browsers localhost will then show the new version after f5.
But after some time it stops working again in that given file.
And i need to repeat this.
I have tried:
Restarting the computer.
Reinstalling Firefox.
Renaming the given file im using each time.
Running sudo apt get update/upgrade
All to no avail.
It's like there is some cache storing the file and Firefox has just stopped updating that cache as I update the file.
Chromium appears to have the same problem.
I pressed f12 and there manually cleared several of the storages and that appears to solve the problem. But only temporarily. After a bit of time, its back.
It's like its emptying some cache, which once filled. Does not get updated again.
My OS is Linux Mint, 20.2.
And my browser is Firefox, version 100.0.
What's going on, how can I solve this?
Is anybody else having this issue?
Also, whatever the solution. I can expect this to be a problem for anyone trying to use my website. Question is how I can possibly solve this in a manner that solves this for anyone using my future website as well.
I think I found the solution
In Firefox, go to:
about:config
And set the following values:
browser.cache.disk.enable = false
browser.cache.memory.enable = false
network.http.use-cache = false
I think , you should try removing userdata from /home//.config or /home//.config Search for Mozilla or Firefox Folder
For firefox I like to use the Clear Cache addon, especially when doing web development in order to get the most recent version of pages. You may also look at changing the way your browser caches by modifying your code, as outlined here.
I have multiple instances of site that share the same database. I've run into an issue where I reverted a page template to its previous version and on the current site instance it looks good, but on other instances it is still uses the old version. I tried restarting the application pools, sites, database server, but it still does not reflect on other instances. I've tried Kentico's System application to restart the application, clear cache and release unused memory, but nothing works. My Kentico version is 12.0.29.
What am I missing, could you please advise on my case?
After reverting template i needed to check-in some changes that CMS made, and after pulling code my sites are the same again. Seems that Kentico saves some changes to files?
Kentico caches very heavily and this is most likely the issue you're seeing. When you say you have multiple instances, are you talking codebases or what are you talking about?
In the other instances, if you want to see the changes immediately, you need to go to the System app and clear the cache. This should help you see those changes a lot faster.
Kentico caches the data heavily as Brenden said. as per my understanding the template versions you need to verify.
If the versions are same you need to go to system module thenrelease the memory and clear the cache of the system.
We frequently use Excel to perform bulk updates of data in TFS. Up until very recently, the Team Foundation Add-In has worked very well. However, it has started failing in several ways:
It will connect to the server, but attempting to connect to any
project causes Excel to crash, producing a Watson report in the
Windows Application Event Log.
If I restart Excel, it reports that it is running into problems with
both the shim and the add-in, and offers to disable it. If I do not
disable it, I still can't connect to a project.
Eventually, the add-in refuses to load at all, until I use the
Options dialog to manually add the COM add-in back into the
application. Doing so produces the same results (Excel crashes when
attempting to load a project).
I have taken the following steps in an attempt to resolve the issue:
Removed and completely reinstalled Office.
Re-registered the add-in component.
Uninstalled and reinstalled Team Foundation Office Integration.
None of these have produced a fix to the issue.
Does anyone know how to resolve this issue?
P.S. If this is not the correct "stack" for this question, kindly point me to the correct one on the exchange. Thank you.
If you are reading the accepted answer and it still isn't working, here's an additional tip. I had the EXACT same problem and saw that same link to clear the cache from numerous sites, bit it didn't work.
Here's the thing. I don't think that article lists ALL of the places that cache can be hiding on your machine. I deleted the cache folder in two different places on my machine and had given up on that as a solution.
Then I searched my entire hard drive for any folder with "Team Foundation" in the name and found a couple more buried in other hierarchies. Deleting these FINALLY solved the problem.
Here are some folders to look for, but like I said, check the entire drive
c:\users\yourlogin\AppData\Local\Microsoft\Team Foundation
c:\Program Files\Common Files\Microsoft shared\Team Foundation Server\
c:\users\yourlogin\AppData\Local\Temp\Microsoft\Team Foundation
The actual cache folder will be nested another level deep under a numbered folder named with something like "7.0" or "8.0" delete the cache folder from every one you find under every number.
In general cleaning the caches on your client machine will resolve such problems, including the TFS and VS caches...
To clean the caches, please see How to clear the TFS cache on client machines
I just came back from MWLUG and started to open up some Xpages DBs to work on, when all of the sudden I am getting 1000s of errors like this:
I googled the issue and I believe it has something to do with the path of the org.eclipse.pde.core.requiredPlugins.
When I opened up the packages and looked at fixing an error I got this:
The problem is that I do not know what the correct setting for this should be, or how to fix it. The apps run fine, but obviously something is wrong.
Any help would be very much appreciated.
Bryan
==================================================
I may know more about the problem. In designer when I go to File==>Application==Application Management this is what I see:
A different install has several components under it.
I updated my designer and client and admin to 9.0.1 FP4 last week. That is the last thing I remember doing before this messed up (along with installing the Debug Toolbar).
How can I fix my designer install?
Strange indeed, you should check your hard drive for bad sectors.
Looks like a broken DDE in general. The plugin XML file maybe broken so the app manager doesn't show you the plugins installed. Therefor I assume DDE starts very quickly, right? Because nothing is loaded.
I had this before and my "solution" was:
de-install DDE and Fixpacks
delete workspace folder
re-install DDE and Fixpacks
re-install plugins ad setup workig sets
This is a pity but at least you get a clean install. You don't have to delete everything (e.g. the DATA folder)
The following issue just crept up on me. The steps mentioned below had worked just fine until about 2 days ago.
When I deploy a update to a solution (of web parts) to a SharePoint 2010 server I don't see the update. The solution does get installed, but from what I can tell the installed web parts are over a month old (nothing new is installed).
I do the following steps through PowerShell:
retract the solution from the web app
remove the solution
add the solution
install the solution to the web app
I have tried restarting the Web App, restarting IIS and also restarting the server. Nothing seems to work.
I notice that after I remove the solution it does get removed from the GAC. After I add/install it the solution does reappears in the GAC.
Am I missing something? Am I overlooking a step that I should be doing? Something to try?
I never deactivated/reactivated the Feature.
After following the same steps I mentioned in my question I just deactivated, then reactivated, the Feature and everything started to working fine.
This is an easy thing to I can start to implement with my solution updates. However, why did I never have to do this step before?
In general, you should check your ULS log to see which version of your solution is running. If you see the old one, then you can be sure that your activated site feature is still bound to the old version. In this case you have to Inactivate the site feature indeed to loose that tie and then Activate to bind to the new one (it appears Activate always ties the site feature to the newest version of the solution).
Maybe you had not to do this earlier, because you did not change the version number of your solution, appearing as the same version in GAC on the server. In this case you had your site feature already pointing to the correct version of your solution, therefore didn't have to reset the feature.
You have probably checked, but just in case. Make sure that the powershell script is not adding a month old package.
Is the problem in the web part code or the configuration? The configuration usually unghosts itself sooner or later and refuses to update from the solution - you can update the file in the gallery manually if anything has changed there. For most updates there won't be any changes because existing web parts won't get updates applied anyway - they will use new code but old configuration.
If the problem is the code itself, does the assembly appear to the system to be unchanged? All the hardcoded full name references in SharePoint config files mean that usually you are deploying a new assembly but with the same version numbers. This can mean that the system doesn't bother making the update. I have found it very useful to update AssemblyFileVersion (which does not affect binding) on every build and have a page in _layouts that displays the file versions of all the loaded assemblies so I know exactly what is running.