My website worked correctly until last week, when suddenly lots of "not found" errors appeared. The error message is visible but I cannot find the reason. The errors stated that the pages that are unable to be found are linked from sitemap.xml, however prior to the errors appearing Google was able to crawl through the website correctly. Here is an example:
Real link in sitemap (This is the old link that is still functional):
https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html
What the search console is actually pointing to:
https://rohamweb.com/webdesign/174-
Apparently the crawlers cannot read content after -, likely due to the different language. I have never encountered this issue until last week, in which perviously was functional.
Thanks in advance for the help!
If this is the actual link :https://rohamweb.com/webdesign/174-طراحی-حرفه-ای-سایت-در-تهران.html, you are doing it wrong and it should be URL encoded before sending it to the response:
https://rohamweb.com/webdesign/174-%D8%B7%D8%B1%D8%A7%D8%AD%DB%8C-%D8%AD%D8%B1%D9%81%D9%87-%D8%A7%DB%8C-%D8%B3%D8%A7%DB%8C%D8%AA-%D8%AF%D8%B1-%D8%AA%D9%87%D8%B1%D8%A7%D9%86.html
In this case, all of the available engines are able to follow it.
Related
I'm working through some issues on semrush and they've highlighted that I've got duplicate title and meta descriptions on the following URL types:
domain-home.com/
domain-home.com.
I don't know how the second url would've come about so I'm not sure how to fix it. I can't see anything in the htaccess that would've generated that . after the domain so I'm not sure how to fix it.
Does anybody have any ideas?
Thank you
It turns out the reason was because the client had included a link to the home page in the text of one of their pages that had a full stop within the href.
This caused the issue for semrush.
Next time I'll think about whether or not the reason could be simple human error rather than some more complex reason.
I am using homestead as my development environment, I turned on the hhvm option for the site
sites:
- map: homestead.app
to: /home/vagrant/Code/wheremyprojectis
hhvm: true
I found that when there is an exception, everything is fine, but If I forgot to use namespace, got syntax error in the blade templates, I got nothing, blank page. I go check the logs and still nothing, the debug option is true. It's quite frustrating until I turned off the hhvm option.
I know it is not a big deal, but I still want to know is there any way to fix this?
I experienced the same problem. I searched around and found that it seems to be intentional:
https://github.com/facebook/hhvm/issues/4818
https://github.com/facebook/hhvm/issues/2571
Now you can poke through the github issues mentioned above, as well as these stackoverflow questions:
Display fatal/notice errors in browser
hhvm-fastcgi + nginx how to make it display fatal errors in the browser
laravel 5 show blank page on server error (and no laravel log), running with hhvm and nginx
For the time being, it ultimately boils down to writing your own handler, which isn't too bad. You can also tail the errors at /var/log/hhvm/error.log. Any errors that you intentionally want going to the browser you could of course handle using Laravel's error handling and logging.
UPDATE:
I reported this issue(and a fix) to the Laravel github here:
https://github.com/laravel/framework/issues/8744
We have never experienced this issue in Umbraco 4, but we've got this twice in Umbraco 7.
The Problem
So we've got a page: www.mywebsite.com/sale
It has been working for a month, then suddenly it shows 404:
The (non-ideal) Solution
We could change the template of this document, eg. from SalePage to TextPage, then back to SalePage.
That will temporarily fix it.
But after IIS restart, or after republishing the page, it will show the 404 error again.
For a permanent fix, we have to change the page name, eg. from Sale to Sale1.
The Question
Sometimes changing the page name is not an ideal solution at all.
Has anyone experienced this? Or know where to look? May be the database has a corrupted entry somewhere..?
We found the problem! We have this structure under Content:
Home
HomeSlide1
HomeSlide2
Pages
Sale
About Us
etc
The problem started when someone created a "home slide" under Home called "sale".
So, both Home/sale and Pages/Sale has the same path: /sale/
Deleting/renaming Home/sale fixed the problem.
This sounds like a corrupt cache.
To find out what went wrong:
Investigate the xml config (/config/umbraco.config)? I suspect this file will still contain the correct information.
If the umbraco.config file doesn't contain wrong elements, check the examine indexes. When you do a "rebuild indexes" from the developer node in the umbraco backend the problem might go away also.
If you know what is going wrong, you can start finding a solution for fixing the issue. E.g. finding out which action went wrong.
I have a page where I have a link with an ics file.
Using safari the problem is that when downloading and importing the event into the calendar is showing the wrong event, precissely an old one.
The strange situation of this is that obviously some cache or trace from the old file is getting gathered instead of the new ics file, more strange to me at least is the fact that I deleted everything like cache history, calendar entries, etc. , even changed the URL to an invalid one and then does nothing, and the correct one still remains with the old event information from 3 months old.
I tried searching here and internet about reason of this behaviour but I havent find any logical reason.
I also changed all settings under icloud and under Mail,contacts, Calendars without success.
Does anyone knows about this weird behaviour Im facing?
Ok I solved my problem.
The issue was the UID on the .ics. Needs to be Unique and I had it repeated.
Probably is a "stupid" reason but got me crazy. I leave this for someone who would have this kind of "stupid" issue in the future.
I've been having this error over lot of modx evolution 1.0.5 installations (I allways use 1&1 servers, in Linux version) It fails to load the home page (not any other pages) it seems that every time I clean the cache, via the manager or via API code, it creates again this file in the cache:
docid_1.pageCache.php
But the thing is that even if the folder cache and all the files inside are set to 777 permissions when it creates files for caching they have any permission set and that's the thing causing this error.
Anybody has had this error? I've been searching in MODX forums but didn't find anybody worried about this, but still I can see it's something happening a lot since when I search on google this error, I don't find forum posts discussing this but instead lots of modx frontend pages showing this error at their home pages.
Maybe it's a problem with 1&1 PHP configuration.
I'm really worried about this cose it has happen some times when I client calls me "über mad" complaining about his home page showing this error.
I've seen that new 1.06 version has some fix on the pagecache parser but I don't know if it's related to my problem.
Here's the error page:
« MODx Parse Error »
MODx encountered the following error while attempting to parse the
requested resource: « PHP Parse Error »
PHP error debug Error: file(assets/cache/docid_1.pageCache.php) [function.file]: failed to open stream: Permission denied
Error type/ Nr.: Warning - 2
File: /homepages/3/d405318697/htdocs/t3st/manager/includes/document.parser.class.inc.php
Line: 413
Line 413 source: $flContent= implode("", file($cacheFile));
The cheeky answer? - "upgrade" Evolution is dead.
A more helpful answer, check the modx system settings, in Revolution you can tell modx what permissions to attempt to set on files, my guess is that maybe you have inadvertently set these to 000 if that's what you mean by this: "they have any permission set"
If that does not work/you get desperate, disable all caching and test or if possible [still not familiar with evo] set that resource to not be cached.
Though something odd is going on, please confirm; the index page will be cached but with no permissions i.e. 000, subsequent pages will be cached but do have correct permissions set? i.e. 666 [or 644/whatever]