We use AEM 6.0 for a client and crx/de goes blank every now and then.
Not sure why and the frequency that it happens , but on a random check of every 3 or 4 hours the crx/de page of a publish instance does not even load the crx/de page , it just shows blank.
Unable to get the logs as it is a restricted environment(sorry about that) , but the error shows - crx/de - Resource not found.
Related
We're working on implementing GPT into our SPA written in VueJS. Whenever a user navigates to a different page we call googletag.destroySlots(); for the slots we want to remove, before the DIV element is removed from the DOM (beforeDestroyed hook in VueJS, removed the google.cmd.push())
The issue is the following error shows up in the Google Publisher Console:
googletag.defineSlot was called more times than there are DIVs in the DOM associated with ad slots while in Single Request Mode. This will impact impression counts.
Besides the warning the Ad Slot will still show up as overlay and in the Ad Slots section of the Console, closing and reopening the console doesn't work.
I've tried the following to reproduce it:
Define a slot with googletag.defineSlot
load in an ad using prebid then googletag.refresh (shows fine)
Call googletag.destroySlots()
Remove the DIV element that was linked to that slot
Started Publisher Console
In this scenario the warning appears and the Ad Slot is listed in the console.
So my question is, should we ignore this warning? Because we are properly calling destroySlots, and the slot isn't listed under getSlots(); either.
Some Time ago our users reported problems with sharing content from our page (text/image wouldn't show up in the share dialog), after some research we added the og:image:width and og:image:height-tags. To reduce loading time, the facebook-scraper receives the page with an empty <body> (we had troubles with timeout too).
Everything worked great until about a week ago. Pages that have already been scraped showed errors in the Object-Debugger:
Error parsing input URL, no data was cached, or no data was scraped.
This error shows up nearly everytime i click Show existing scrape information, eventually it would go away (without re-scraping the page) but then following error shows up:
The 'og:type' property is required, but not present.
The Sharing-Debugger additionally shows following error:
The parser's result for this metadata did not match the input metadata. Likely, this was
caused by the data being ordered in an unexpected way, multiple values being given for a
property only expecting a single value, or property values for a given property being
mismatched. Here are the input properties that were not seen in the parsed result:
'fb:admins, og:type, og:description, og:title, og:site_name, og:image:url, og:image:width,
og:image:height'
Sometimes it also says that our images are too big and couldnt be downloaded, but the image is shown in the preview. Sometimes it even goes as far as showing
Could not scrape URL because it has been blocked
What doesnt add up here is that if i click on See exactly what our scraper sees for your URL it shows me the source of our page with empty <body> and <og:...>-tags in the <head>
The debugger shows me the correct og:url, og:type, og:title, og:description and og:image, the preview is alright, response code is 206 and last scraping was somewhere in August.
After rescraping a few times, most of the time the error messages are gone, but that cant be the solution. It seems as if the debugger sends random errors for whatever reason
So what do these error messages really mean? Are they wrong? What am i missing here?
(Note: a 3rd pary is having trouble sharing our pages in their application due to those error messages, everytime they appeared in the debugger, their data seems to be somehow broken)
After some back and forth with one of facebooks supporter in the developer forum, they acknowledged my problem as a bug and assigned a team for further investigation. However, a few days later my bug report was closed with following message:
Those messages are due to a bug in our Debugger when you scrape no-canonical URLs. On that case, the information about your URL is updated asynchronously so it takes a little while for the error messages to go away.
If you input the canonical URL in the debugger, the error messages will go away after the first scrape.
Unfortunately, due to the way our systems works, we are not planning to fix that error in the near future.
I am using SEO Layered Navigation Plus < http://www.manadev.com/seo-layered-navigation-plus > in Magento 1.7. Few days age, I have put some demo products and it was working fine but when my site goes to live server and I have deleted all the products then it is not working.
Suppose, I have a attribute "Color" with two option White, block etc. Now I click on white then the products are not filtering but the url is changing. Now the strange thing is - After that, if I am refreshing the page then it will redirect to 404 error page.
Please, help me out.
I think you should check the following:
Make sure you unsecure, secure base URL is pointing correctly to your live website and try to flush your Magento cache storage.
Are you using the latest version of the extension ?, maybe you should check for any new updates, the last version was 3.10.
Last week suddenly the XFBML login button stopped working on our site. Instead of showing a nice FB login button, it just shows the button text. In Firebug, I'm getting an error:
TypeError: k.root is null
Strangely, the problem occurs on our production environment, test environment and my own development environment. The production environment hasn't been updated or changed for quite some time so it's not code changes on our end. All three environments also connect to separate Facebook apps, each with a different appID, so it also can't be a (accidental) configuration error with the Facebook app.
Does anyone know if it's perhaps possible that this is an issue on Facebook's end? They did do a compatibility breaking update on 5th of September, but as far as I can see, the changes are not related to the login button.
Anyone know what could possibly cause this?
This was a bug that would occur if you called FB.init prior to document.body being defined, (as in the HEAD), this has now been resolved.
I started to face this issue last week as well. I managed to solve with one of the options below:
1) The app's 'App Domains' was misconfigured (it should be a domain name and not a full URL):
Source: https://developers.facebook.com/bugs/225729134220754
or
2) Just replace the div (containing class fb-login-button) with a regular button to call FB.login, and all the things will start to work again.
The like button on my site was working fine and had more than 270 recommendations but suddenly they disappeared and when I click on the button, it gives an error:
This page is either disabled or not visible to the current user.
I checked my URL on the debug tool but it gives me the same result each time that appears to be fine.
I have no idea what is the problem or if my site has been blocked by them.
How can I check if its blocked or find the problem?
My URL is: iran.us
Check this link: http://developers.facebook.com/tools/debug/og/object?q=http%3A%2F%2Firan.us
As for your counts, you specified
http://iran.us (http://graph.facebook.com/http://www.iran.us)
and the counts you're looking for are under
http://www.iran.us/index.php (http://graph.facebook.com/http://www.iran.us/index.php)
The fix for this is your plugin code.
Add data-href="http://www.iran.us/index.php" to the plugin code and it will be back to the old like count. You will not be able to move the 6 current ones over though.