I am developing a Magento site.The url of the site is like http://www.xyz.com/index.php/
But some of the images are coming from secure url
https://www.xyz.com/skin/frontend/default/mytheme/images/logo.png
The images which are having https:// are not visible in the frontend.
Till yesterday the site was working well and images were not coming from https:// url. I think at client side they done some changes and problem arise. How to find the cause of problem.
I get something like that in browser.
Related
I developed a web app in VueJS, but it seems to be having some issues with CloudFlare.
When a user is prompted with the Captcha verification screen, upon completing the verification the page loads, but it is blocking resources like my JS files.
However, if I say whitelist a certain country and access it, the page works as intended.
I've also had some issue when changing certain elements and the page not updating correctly, even when purging. I feel this issue is related to the one above.
(I'm also using SSL if that makes any difference.)
Out of curiosity, I've recently seen a lot of pages using a “newer” 5 second protection style page rather than a captcha. I was wondering if cloudflare offered anything like this as I feel the captcha gets very annoying for my users.
Thanks and any help is appreciated.
I've deployed a React Redux site on hostgator.com. While it works to visit the page and navigate as usual. (React routing works), it shows 404 not found whenever I reload the page.
I talked to their support which, before leaving 20 sec into the conversation, came with the suggestion that it may have to do with the site trying to run on https, while no SSL is implemented.
I'm curious, why does it work locally and not on the world wide web? Any thoughts?
Thanks.
You need to look into a Server Side Rendering solution. A good framework for doing so with React is Next.js.
Basically as long as you don't refresh the page React-Router has control over the address bar as well as history via the History API. But when you hit refresh you send a request to the server for whatever is in the address bar. But the server is not handling your routing, React-Router is on the client side. You also won't be able to type a child route directly into the address bar without server side rendering.
I have this reactjs webapp - http://52.26.51.120/
It loads a single page and then you can click links to dynamically load other boards on the same page... such as 52.26.51.120/#/b, 52.26.51.120/#/g
Now the thing is, I want each of these to be an individual page, for the purpose of seo. I want you to be able to google "my-site.com g", and you will see the result 52.26.51.120/#/g. This obviously cant work if you are using reactjs and it is all on one page. Google will only render and cache that main page (can it even render that page? does google execute javascript?)
Even more specifically, id want something like my-site.com/g/1234 to load a thread. There could be a thousand threads every day, so im not sure how to handle that.
Are there any solutions to this? to allow react to possibly serve up static pages as html so that they can be cached on google? I am using expressjs and webpack as my server right now, and all the code is executed in jsx files.
Thanks
You can use Prerender.io service. In a nutshell you will need to connect your server app or web server with prerender service and do little setup (see documentation). After that search engines and crawlers will be served with a static (prerendered) content while users will get classic React.js (or any other single page) app.
There is a hosted service with free tier or open source version
I suspect you could do some smart configuration with nginx and it could convert a url of domain/board to a redirection of domain/#/board when detecting the user-agent as a bot instead of a typical user.
This issue began last week. Prior to that, I was not having any problems, and I am not aware of any changes to my site or platform.
Now, when I want to share a new blog or article to Google+, it fails. Typically I would use the embedded +1 buttons on a specific post and use the expanded box to create my post. The box comes up, but instead of a nice title and image, it now uses the URL only for the page, and sometimes adds extra characters to the end of the URL. If I take the URL from the address bar and try to compose a new update directly on Google+, I get the same issue. If I enter the URL into the Link field on a status update, it usually comes back "could not load website."
Here's a sample
You'll find Google+ sharing buttons above and below the article. Sharing to every other network works as expected.
My site is a Drupal site that has been operating for 10 months. I am a Drupal developer, but have never encountered an issue like this.
It appears that requests from the Googler crawler are being rejected by your server. I tried testing the microdata with the structured data testing tool and it runs into problems connecting to your site. Other sites work fine.
If you have access to your site's Apache access logs, I would check those for problems coming to that URL. You can narrow your search down by looking for the user agent of the crawler: Google (+https://developers.google.com/+/web/snippet/)
My guess is that something changed in your server's configuration that is the cause. Start with the logs and see what's there.
I have a website which has an SSL certificate installed. If I navigate to the site via https://www.[MY-SITE].com then it flashes up in Chrome for a second with a green https:// indication. Then it greys out and shows the message that the site is loading up insecure content.
Some of the links on the site are still the old http:// versions but it isn't actually loading anything from the files it is linking to. One thing I thought of was that I don't have access to change the Google Analytics code to the https:// so it is still on the http:// in the admin settings on Google. Would this be the issue?
Thanks,
Jack
It may occur mistakes I think. I just search out some post from web regarding your queries.
please read this link :
http://blogoscoped.com/archive/2007-12-13-n83.html
http://code.google.com/p/r-google-analytics/issues/detail?id=1
I hope it will be helpful for you.