Supersized and Zurb's Foundation 5: slides are unclickable - zurb-foundation

://50.22.11.18/~luxuryvi/
I have some success pairing Supersized 3.2.7 and Zurb's Foundation 5 except that the supersized background images are unclickable despite the "url:" parameter in the call.
I know it may have been the z-index being a negative number and lower than everything else but I am just wondering if anyone happens to have seen a fix or perhaps manage to get round the issue.
Any info is highly appreciated. Thanks!

Related

DevTools failed to load source map, chart.js behaving abnormally

This is my first javascript project, so I apologize for being ignorant of basically everything.
I made a basic data site for a hobby which has been up for a couple weeks now without incident. Today however I saw that it was behaving strangely: the chart I made is stuck in a loop of shrinking to a single point, and then maximizing, and then shrinking again. The site has been made unusable.
No changes have been made to my code in 12 days, the behavior started some time in the past 24 hours. It's the same in Edge.
Chrome console:
DevTools failed to load source map: Could not load content for https://cdn.jsdelivr.net/npm/chart.umd.js.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
Loading that URL in Chrome shows the same, so OK, it's not there. Can't argue with facts. But I guess it used to be? Why is it not there now?
I've integrated chart.js as follows
<script src="https://cdn.jsdelivr.net/npm/chart.js"></script>
<script src="https://cdn.jsdelivr.net/npm/chartjs-plugin-annotation#2.0.1/dist/chartjs-plugin-annotation.min.js"></script>
And here's the site itself:
https://rejetme.com/
I legitimately have no idea what changed. I would appreciate any help getting back on track here. Thanks.
Ok, classic rookie mistake. Big surprise, I know. It turns out that chart.js just updated to v4.0.1 two days ago, and includes some breaking changes.
So I pinned the version of chart.js that my site uses:
<script src="https://cdn.jsdelivr.net/npm/chart.js#3.9.1"></script>
I guess another option would be to host the libraries locally, but ain't nobody got time for that. I'm going to mark this as answered.

Why hooks of Vue 3 in WebStorm are grey out (Unused function created)

As on the screenshot, a lot of hooks are grey and I don't know what the problem is. I don't get the problem for Vue 2 but for Vue 3.
Can anyone tell me what is the problem?
Known issue, please follow WEB-38671 and linked tickets for updates
I can only suggest suppressing the inspection per instructions in help

Foundation Zurb visibility classes

I am using foundation zurb version 4. I am using foundation's visibility classes. I am using hide-for-medium-down and show-for-medium-down for displaying 2 different headers. Its working fine with ipad in both verticle as well horizontal. But when i view the site on monitor with resolution 1024*768 (ipad also has same resolution of 1024*768), both header gets displayed on monitor.
Plz help me.
Make sure that your browser is supported. Support list
Notice that the IE8 has some caveats

Cant change the order of Sitecore presentation items - Sitecore.NET 6.6.0 (rev. 130404)

I am looking at a content item with many renderings.
I need to move one of the rendering down so it show lower on the page.
I can move it in the Edit presentation settings but as soon as I click ok, the order remains unchanged.
Note, it does work sometimes but is intermittent.
I have looked in the logs and nothing seems bad apart from this:
1032 11:20:45 WARN Long running operation: renderContentEditor pipeline[id={E23237A3-1FEB-4E9A-AEB6-543807ED6CAD}]
I feel this might be a Sitecore bug.
Has anyone experienced this before?
There was a similar issue in 6.5, but I assumed it would have been addressed in an update. Basically, the issue is a result of presentation setting deltas at the item level incorrectly merging with the standard values presentation settings of the item base template.
I would suggest contacting Sitecore support for a workaround or solution. Reference case #387488 and provide detailed steps to reproduce the issue.

Django Debug Toolbar - Which version has the green panel that docks at the top?

I turned on my debug toolbar and was surprised to see the stock template where the panels are aligned to the right.
I upgraded to django 1.3 and re-installed most of my requirements via PIP, which is where I imagine my usual toolbar disappeared.
I had always thought it was David Cramer's fork that had the green panel bar docked at the top, which I find insanely more usable (doesn't obstruct anything), plus it had some default default panels like unique SQL counts.
Now that I've cloned both David's fork and Rob's original, I see neither have this green dock.
Am I going insane? Is this a setting I've missed, or perhaps a different fork? I would kill for the workflow I'm used to!
Update: I've looked through the commits, and indeed, there was a version in 2009 that was docked at the top, but had nowhere near the functionality that the version I'm talking about had. The exact commit that moved the toolbar to the right appears to be: https://github.com/dcramer/django-debug-toolbar/commit/565b100f9d97214043ae93c51d276951a65331e8
But nowhere can I find this awesome version below:
It also claims to be version 0.2 which I find odd too. I will keep going through each commit but any help would be appreciated.
It used to have the bar at the top. The new version has the new sidebar layout.
Update:
I tried to find out which version it was, but found this page where you can download older versions.
https://github.com/robhudson/django-debug-toolbar/downloads
Update2:
Here is the commit where he moves to the side panel 8-11-2009. Yeah a long time ago. I guess it has been a while since I upgraded as well :)
https://github.com/robhudson/django-debug-toolbar/commit/565b100f9d97214043ae93c51d276951a65331e8