I've been using Underscore to create a Wordpress theme. I'd like to use Data-Interchange to swap out layouts for mobile and desktop viewport sizes. When using an adding an image on a small screen (via interchange), the image shows up as it supposed to. However when attempting to change layouts based on viewport size - chrome's dev tools give me a 404 for the page.
The image and the .php page both have the same ownership and permissions. I've used this page as a guide but, still cannot get this to work.
Even if I change the .php file to .html, I still get a 404 on either.
Also, the .php file shows up as an XHR while the image shows up as text/html.
Does anyone know how to fix this?
Related
I followed this tutorial which is perfect for my NextJS website.
The problem is my unsupported.html file has images in it. The images 404 because according to the redirects everything except unsupported.html will redirect (including the images).
So here is Chrome vs IE. So Chrome works because I manually went there and it won't redirect anything because it's not IE.
How can I add to this part source: '/:path((?!unsupported.html$).*)', to say don't redirect unsupported.html AND anything in the /public/images/ folder?
Thanks
This feels close
source: '/:path((?!unsupported.html|.*images*$).*)',
Does this work for your site?
source: '/:path((?!unsupported\.html$|images/).*)',
The key bit is dropping the $ anchor from after images, so it doesn't have to (not) match the actual image name
I hosted a small django project on virtual machine on digital ocean. Before I started using digital ocean to serve static files everything worked fine. But immediately I created a storage space and push my static files there the static files are not being served on the webpage, including django admin page (the project pages are showing net::ERR_ABORTED 403 (Forbidden). I have already installed django_storages and boto3.
I got some hint as to the possible cause of the problem when I clicked on digital ocean aws bucket url that looks like https://django-space-storage.nyc3.digitaloceanspaces.com. When I cliked on it I got the following error:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
It seems the browser is rendering my django pages as xml instead of html. I might be wrong with this assumption because I'm finding a hard time trying to understand what is actually going on. My question is, how do I cause the browser to render my django pages as html instead of xml?
We're using the Vimeo API for a client to play 3 different 360 videos through Android and iOS apps - in some cases we had to make some exceptions in our app to work around special characters in the URL that were causing problems with our player - so we have some code to tidy up the final video URL.
This worked fine, at first, but now it seems as if the Vimeo API is returning different URLs for 2 out of 3 of our videos. Videos from fpdl.vimeocdn.com work fine. They all used this domain when we first created the app. But two of our videos changed to gcs-vimeo.akamaized.net and have a different syntax.
Is this something we can't control? Will the CDN targets change often? Will all 3 of our videos eventually change to the new URL? Before we go back and adjust code again - I need to evaluate if we should just use a different player instead, if this will happen frequently.
Vimeo uses different CDNs to host video files, and those CDNs should not matter to the viewer/enduser.
When getting the direct video file links (either using the API or from the video's Settings page), those links are HTTP 302 redirect links to the actual video file resource. The location of that resource changes every few hours, so always make sure you use the redirect URL provided, and make sure the player being used supports redirects.
I have a bizarre issue with one of my Sitecore sites. Most (but not all) of the images in the Media Library are not displaying in Page Editor/CM. When I view my site in Page Editor or go to mysite.prod-cm.com, the images just show the broken image icon. If I try to go to the image directly, such as mysite.prod-cm.com/~/media/Upload/exampleImage.ashx it returns an error page. However, if I go to the same path on CD, mysite.com/~/media/Upload/exampleImage.ashx, the image displays. In Sitecore, in the master database, I see all my images, I am able to preview them and download them and there appears to be nothing wrong with the files.
I checked the logs to see if there were any useful clues about why the image paths are returning an error, and I see the following message
"WARN Protected page accessed with no current user".
Is this a security setting in Sitecore? This only started happening recently, is there a way to unprotect the Media Library? Like I said, some images still show up, but any new images I add appear broken. The only other message in my logs is
"WARN Memory usage exceeded the MemoryMonitor threshold".
To add on, I can view the images by the path with their item ID, such as mysite.prod-cm.com/~/media/C98B4DAC5FBD416CABF0070D087AE5E2.ashx. That works, but the path with the item name does not.
I got a weird problem, my site shows up perfectly in all browsers but when checking cached pages of site in Google, Bing or even Yahoo, all of them shows broken links and images because some links are overridden such as
Let's say direct url is http://www.expatads.com/47-Thailand/ and it shows perfect.
Here's google cache of the same url.
http://webcache.googleusercontent.com/search?q=cache:qFAzM4VMsJsJ:www.expatads.com/47-Thailand/+&cd=1&hl=en&ct=clnk
What I want to know is the best way to reproduce such errors that are visible instead of waiting for search engines to cache and show pages. Since web browsers do not show any error but actually there is path error that cause that.
I'll appreciate if anyone can give me a way that I can reproduce these errors using some browser, software or whatever?
I believe you are mistaken about this being an error. If you take a look at the screenshot of Google's search result for your page, the images are shown.
It appears that Google's cache does not rewrite relative URLs, which makes some sense because it wouldn't always work and some sites might not allow hotlinking, etc. So, all the the resources linked to on your page using relative links won't show up in Google's cached version.
If you would rather see what your site looks like in other browsers you may want to try Browsershots. This will give you screenshots from a huge number of browsers in order to test compatibility.