My website www.999designs.in won't open at once, it shows an error, however it works fine once you refresh it!! I've hosted it on a LAMP environment, does it require any specific server settings??
First it given an error "Can not find the page you're looking for".
I think the cause of the problem is that you initialize the slider with a wrong image file name. Have a look at function.js line 240:
$(['img/woman1.png','img/woman2.png','img/woman3.png']).preload();
If you reload the image for "banner-slide-woman-1" is called woman.png not woman1.png.
HTH
Andy
Related
When I deployed my react website with three fiber, the contents such as my html would show at first before the content in the div start disappearing on the live. The js would load at first and then disappear. The model did not show at all.
Here is the live site:
https://xavi4075.github.io/portfolio/
It was fine before I compiled and exported onto github. I have no idea why this is happening
the development build is currently facing the same issues as the live one .The hosted code is on the gh-pages branch. The only thing that seems to be working is the background.
I did this from gui's response
however this was the response from the live site. It is working now in the development site with the fetch being portfolio/assets/airplane.fbx. how can I get rid of the second portfolio?
The only actionable item I can discern is your model not showing up. This is because the fetch for it is returning a 404 error. I'm unsure if this is the cause of everything else not loading correctly but if you open your console you'll see something like this:
Console error
I believe if you change the fetch from https://xavi4075.github.io/assets/airplane.fbx to https://xavi4075.github.io/portfolio/assets/airplane.fbx. Your model should show up since that is where your model lives in your files.
I am working on a personal project for my portfolio and I'm completely stuck.
I have an Angular 14 app I've been working on. The stack is PEAN. I currently have a live version of it hosted on Heroku. The issue I'm running into is that in my local development version of the app, everything works as intended, however on the live version on Heroku, If I refresh the page using f5 while on the main backlog page, it does not refresh, and instead shows a blank page with "[ ]" at the top of the page. Every other part of the app functions fine, and it does not fully crash when I run into this issue. If I type a different URL in and go to that page, it works again. If after doing so, I click a link that loads the crashed component, it will reload just fine. It appears that the component only breaks if I refresh the component with f5 (or clicking the refresh button on chrome).
I've been working on this for a long time and I think I've narrowed it down a bit. So far I've:
confirmed that my express server is serving my static HTML files from their folder correctly
added a catch all code block at the bottom of my express file to redirect to index.html
made sure that Heroku was actually executing my server.js file
removed potential offending portions of code, like auth/error interceptors and newly added Google Sign-in
I've also:
checked with various browsers/mobile browsers
checked for console errors (there are none)
checked network tab on refresh. (just shows a 304-OK response)
checked Heroku logs. No errors there either.
The issue can not be recreated locally, and it only happens on refresh of one component, the Backlog component.
If there is any more info I can add please let me know, I'm hoping this is a regularly encountered issue. I can't seem to find anything that specifically deals with my exact issue by searching. Any help is greatly appreciated.
update
The blank page with "[ ]" appears to be my database's response when hit without a user ID to check against, and return data. I've narrowed this down to an HTTP-INTERCEPTOR that injects the user ID into the headers, which the route that would use that info for the DB wouldn't have. This makes my DB return "[]".
The only thing I don't understand is that this happens only when hosted on heroku, and not locally.
Been going round and round on this one. Not a new issue but struggling to identify exactly why LinkedIn doesn't like my images and everyone else does. Facebook and twitter show ok with it
At first thought might be meta issue or cache issue (am familiar with the clear method) or image requirements stated by LinkedIn but ruled all that out. The ssl is a free one but soon to be using a wildcard as facebook didn't like it to see if that has any effect.
The image server uses node js express to deliver static files.
If I just share the image, that shows an error of: "Cannot display preview. You can post as is, or try another link." which points to the server and image to me instead of the website.
The site and images are on different servers with different setups.
Main url is https://rocketthomerentals.com/property/5-bed-house-to-rent-in-newcastle-under-lyme/102750000371
with the image of
http://media.estateapps.co.uk/487/102750000371_IMG_371_1_large.jpg
Anything else I can try? Should be getting the new wildcard SSL sorted early next week but posting here to see if there is anything else I am missing I can try to see if that has any effect.
Thanks
For anyone who's gone around in circles about this issue, was resolved by defining the content type as image, it was missing from the server config.
I am following this code sample to create my own CORS-proxy server. It works fine but when I click a link, I go to an invalid link.
Say, I loaded localhost:1377/?url=www.github.com in my server, the page loads.
But when I click any link (say open-source), I end up going to http://localhost:1337/open-source rather than localhost:1337/?url=http://www.github.com/open-source
How can I handle the requests to stay within my proxy server and keep browsing?
Thanks
Edit: Pictures
Because of anchor tag of Open Source link. You need to parse the DOM.
I'm trying to get the Spotify Hello World app running (https://developer.spotify.com/technologies/apps/tutorial/) and when I run the app in Spotify it doesn't load anything. Using the Inspector, it shows nothing in the head and body of the HTML. I've verified time and again that there actually is something in my index.html file.
I do have a developer's account and I am a premium member.
Does anyone have any suggestions for me to get the app to run correctly?
[SOLVED] I just realized when trying to load the application I was typing spotify:app:Tutorial when it should have been spotify:app:tutorial. It's case sensitive, yet when its the wrong case it doesn't yield any error, just empty HTML.
Seems like your application is found else you would get a not found error. At this rate we can't really tell alot. You might wanna include your manifest and index.html file.
Also if you change something in your manifest you have to kill spotify and restart for it to work properly again.
Using linux (Ubuntu 11.10) the tutorial did not start correctly until I used
consistent caps.
I.e. I changed to "tutorial" instead of "Tutorial" in both app directory name
and in the manifest. Still, the "Spotify" dir in $home needs S in caps.
Then the app started correctly using uri spotify:app:tutorial
I.e. ~/Spotify/tutorial/*
Make sure "BundleIdentifier":"tutorial" is in your manifest.json file.