Sitecore Speak css and js no longer loaded - sitecore

I have a Sitecore 8 Update 2 environment.
For some reason it seems that speak css and js are no longer loaded.
for example: /sitecore/shell/client/Speak/Assets/css/speak-default-theme.css
I'm not sure what caused this and have little knowledge about speak.
Any comments and feedback are wecome.
launchpad
browse media library

Faced the SAME issue when upgrading to sitecore 8.1 , the problem was this step -
The .Sitecore.Speak.Important.config file renamed to 001.Sitecore.Speak.Important.config , new pipelines have been added to it for speak 2.0 upgrade
Once I renamed file and ensured the pipelines were all there as per config fileinstructions(for 8.1 initial version) the styles came back.

Related

Why is my debug Django server takes so long to load on my localhost? I'm using Django, django-compressor, django-libsass and bootstrap

I have a problem with developing a Django website. I started out with using CDN Boostrap and JS as recommended in Boostrap 5 docs but then I wanted to customize the CSS, so I changed the setup to compile Bootstrap's source scss files with django-libsass. I followed the installation guides for django-libsass and django-compressor.
What I discovered is that while everything works, it works very slow on my local machine (5-6s per opening a new page). I'm not very experienced in web development so I'm not sure what could be causing this.
If it's relevant, I don't use a frontend yet and I'm sticking to Django's templates.
I tried to download a sample django libsass project and put bootstrap there and the outcome was the same.
I expected the time for loading the pages to increase slightly due to the fact that now it has to compile scss files but not so much.
Googling turned up no results:(
Is this an expected behavior when debugging from a local machine or am I missing something? Huge thanks!

How to check Which version is installed of Web form for marketer in Sitecore 8

How I can check for WFFM version that have installed in Sitecore 8.
I was checking in List of Package inside Data/Packages folder . Is this correct way to do this ?
That's one of the options, but it's not necessarily correct. One can upload a package to that folder but never install it.
You can also check WFFFM dlls in the bin folder and see their version.
And maybe the most reliable way: login to Sitecore Desktop, change database to core and in Content Editor find /sitecore/system/packages/installation history node. There should be a list of all packages which are installed in your Sitecore application including their versions.
Look in the sitecore general log at application startup, all dlls are listed including version numbers.
I found one more way All Application ==> System ==> License detail ,there i found the version of WFFM.

Update Sitecore and SIP together?

I currently have the task of updating a Sitecore Instance 6.6 with SIP 3.2. The target is reaching Sitecore 7.0, so we can use Item Buckets.
The problem is when I update Sitecore to 7.0, it doesn't work with SIP 3.2, because assembly references doesn't match anymore and Sitecore 7.0 runs on .NET 4.5, where SIP 3.2 runs on .NET 3.5. So the Sitecore Backend does not work anymore and I cannot update the SIP.
If I update the SIP to 4.0 (which works with Sitecore 7.0) before updating the Sitecore Instance to 7.0, I get a similar problem.
Any idea what I can do to update both together? Or is there another way of achiving Sitecore 7.0 with SIP 4.0?
I would recommend uninstalling SIP first. You can achieve this is via removing the code files and configs from the solution manually - you can try leaving the Sitecore Items there as they shouldn't cause issues.
It will be helpful to redownloading the SIP package, unzip to see the files and view which files and configs it contains, then remove those from your solution.
A simpler way if you have Sitecore Rocks is to create an Anti-package - https://www.sitecore.net/nl-be/learn/blogs/technical-blogs/trevor-campbell/posts/2013/02/28-days-of-sitecore-rocks-package-management-part-1.aspx
Once you have removed SIP, complete your upgrade of Sitecore and confirm your site serves correctly afterwards.
Then its a matter of installing the correct version of SIP for the version of Sitecore 7 you have upgraded to. This will mitigate the issue of assemblies being different versions.
I would recommend backing up your databases before the upgrade as best practice but to also retrieve any SIP Item you may later need.

Sitecore 8 Installation Wizard in Development tools not working

After I installed sitecore 8, looks like I cant access installation wizard on development tools. All I can see is blank popup on all the browsers. I checked the log files and could not find anything related.
Any suggestions will be appreciated.
Might help anyone with the same problem.
Sitecore is checking for Packages folder in Data Folder and failed. I don't understand why it can't create one(I checked the permissions all good.)Kind of bug in Sitecore 8 rev. 141212.
Once I created Packages folder, it's all good.
This is probably due to mongoDB not being setup properly.
See this article
http://sitecorejourney.nileshthakkar.com/2015/01/is-your-sitecore-8-stuck-up-while.html?utm_source=feedburner&utm_medium=email&utm_campaign=Feed:+SitecoreJourney+(Sitecore+Journey)&m=1

Silverlight 5 breaking Silverlight 4 application

I recently installed silverlight 5 and started working on new project based on SL5 version but after installing SL5 all my previous applications built on SL4 are not working and when i run these applications, XAP is getting downloaded and I am getting complete white screen as soon as it completed downloading XAP file and getting "AG_E_UNKNOWN_ERROR".
FYI: Everything works fine when i browse these SL4 based applications (hosted on my system) from a different system having only SL4 plugin.
Is there any known compatibility issue exists with SL4 & SL5 plugins running parallel? Kindly let me know any workarounds for this issue?
Thanks.
If you use Binding to Resource Files
You should update the constructor back to the public.
Also it might be possible that you web services references were broken