I have a app in which I created a custom object with custom properties. The object is called "character" and the custom properties are theme (as string) and user (as profile).
I have an action called "vote" which contains a property "character" that references the custom object above.
I created a story that links the action to the object. All the flexible sentences refer to "character.title".
This was working fine for awhile and whenever I published a story I was able to see a preview of it in the story settings. Now I get an error image
I can publish using graph api explorer with no problems. And if I debug a character URL using the debugger tool, there are no errors. Everything looks good, but I can't see a preview and I'm worried that my published stories are not actually posting.
Another strange thing is that I have another app that I use for staging and testing purposes that doesn't have this problem.
I had to click on Edit Attachments in the Story settings and set values for at least one of the fields. I guess without it Facebook didn't know how to render the preview. There should be an appropriate warning message.
Note: my other apps have been working fine without having to fill values in the Edit Attachments window. This app was a strange exception.
Related
I have some Computed Fields and in these fields, I get some HTML codes with simple_html_dom.php class from some sites. Codes works perfectly on pages, but when I try to get these fields to use in a View, Drupal gives the following error.
http://i.stack.imgur.com/W2Rhc.jpg
Anybody can help?
Even if it is not the best solution, after installing Views PHP module of Drupal, problem is slightly solved. I still get the error message on every time I try to change something, also I am having difficulties on making a change on the view, like saving and adding the same thing 5 times and got successfull, still it is a solution.
This message usually appears when you try to save the form before the ajax process has finished.
Try checking the 'network' tab on developer tools installed within Google Chrome or by using a tool similar to firebug. This will show you the request being made via ajax and should give you more information to debug.
I just replaced a tumblr website for a client with a brand new Wordpress site. And when running it through the Facebook debugger, I get this error:
The object at 'http://example.com/' previously had type 'tumblr-feed:tumblelog' and cannot be changed to an object of type 'website' to avoid data corruption of existing actions.
I Googled "Cannot change og_type" (in quotes) and got literally zero results (well now it seems there are results stemming from this question). Am I really doomed to Facebook data mismatch?
Per the error message
... cannot be changed to an object of type 'website' to avoid data corruption of existing actions.
If the og:type were changed for a URL, any existing user posts linking to it or sharing it, any Open Graph actions referencing it, as well as any likes of the URL would become broken and the user's profiles would be missing content they'd posted before.
I don't believe there's any way around this, as it's an intentional restriction to avoid breaking existing posts, likes, actions, etc referencing a URL. If the posts were broken, content would be removed from or mangled on the user's timeline.
A possible workaround if you want to have a 'new' object at that URL is to use my instructions in this answer about moving URLs to put a Like button on the URL you're trying to change (let's call it A), but pointing to a slightly different, new URL (let's call it B) , and then use the redirect mechanism in my answer to bounce users landing at URL B back to A, but serve the metdata describing 'A' on URL B if the Facebook crawler accesses it
Does the client's site have more than 10,000 likes? If so, Facebook doesn't allow og:type to be changed.
You can update the attributes of your page by updating your page's tags. Note that og:title and og:type are only editable initially - after your page receives 50 likes the title becomes fixed, and after your page receives 10,000 likes the type becomes fixed. These properties are fixed to avoid surprising users who have liked the page already. Changing the title or type tags after these limits are reached does nothing, your page retains the original title and type.
Here's the link to the Open Graph documentation. :)
I would reccomend using the Open Graph Debugger to check what facebook really sees and if facebook eventually has a cached version of your site. (you find hte debugger here: https://developers.facebook.com/tools/debug)
NOte that it doesnt say og:type - it says og_type
This is hitting me too since my og:type is set to "shamrockirishbar:shamrockirishbar" BUT the linter is saying og_type (of which there is none in my meta data) is set to "website".
enter link description here
The standard ?google_console=1 isn't working for us at the moment. We're using the Google Publisher Tag (asynchronous).
The Google publisher console is OK for spot checks, but I'd highly suggest moving away from that method. Sometimes the Google pub console will list partial data for ad units...and I have had rough experiences with using the Google pub console for debugging sync GPT.
If you're using Chrome, a stronger method would be the following:
Load the page.
Open the Chrome Developer Tools, and click on the Network tab.
In the filter field, enter "doubleclick" (minus the quotes).
Ctrl+R to refresh the page.
All the DFP ad calls will begin populating (typically have ads and gampad references in the name).
Click on an ad call. The info should display in the right panel.
For quick reference:
iu: (the ad unit portion of the string)
Cust_params or scp: typically most custom criteria targeting values should display in either of these two, depending on tag implementation
Additionally, in the Response tab, under Headers, the Google Line Item ID and Google Creative ID will be listed....this is extremely helpful for debug/troubleshooting. You can also see XML returns for video creatives.
Also, if you need to debug outside of Chrome, Charles/Fiddler are good debug alternatives. Keep am eye out for the Query String and Header tabs, but the same info should pass thru. Filtering is key.
Hope this helps.
Just try to run the following command in JS console:
googletag.openConsole();
Note: You can also specify ID of the div element containing the ad slot in the function argument.
Or paste the following code into the bookmark in Bookmark Manager:
javascript:googletag.openConsole();
then navigate to the website and click on newly created bookmark.
Or use the following HTML code to create a link on your content page, e.g.:
Open console
See also:
Enable the Google Publisher Console
GPT Reference
I've posted this in the Our Umbraco forum (http://our.umbraco.org/forum/ourumb-dev-forum/bugs/30914-HTML-formatting-error-on-workflow-notification-emails) but would like to expand the audience as I need a quick resolution to this problem.
There appears to be an issue with the HTML used in workflow notification emails, property names are displayed but their values are not visible. The HTML content is there and if I save the source as an .htm file and view it in Firefox the values are displayed (although in the wrong location).
The HTML is generated from the sendNotification function in the umbraco.cms.businesslogic.workflow namespace, I am using Umbraco v4.7.1.1 and this problem was noticed in Outlook 2007.
Has anybody else encountered this problem?
It appears that this issue has been logged with Umbraco (http://umbraco.codeplex.com/workitem/26577) but has not been addressed.
The fix is a simple code change, for my current project I have decided to download the CMS source code and make the change myself. This works but throws up maintenance issues e.g. ensuring my change is not wiped out during a CMS upgrade.
I have just installed dexterity into our office's intranet site so that I can create some new types for particular styles of documents. I had hoped just to use just the TTW capabilities, but I'm seeing extraordinary behaviour. When I try to create the fields of a new type, any, or all of the following problems can be seen, almost non-deterministically:
After saving the attributes of a new field, the field sometimes doesn't get shown in the page showing the fields of that new type.
Sometime a page refesh does show it, other times it doesn't.
Clicking on the Settings for a field (when it is visible) sometimes shows the error dialog indicationg that this page does not exist.
Sometimes the settings dialog does come up, and then attempts to save it fail with another error dialog to say that this page does not exist.
With a bit of persistance by retrying and refreshing often, I can get a type defined with a couple fields. Then when If I create an instance of this new type, often only some subset of those new fields are shown in the creation form. When I try to save it, the form is shown again but this time with the required fields that were originally hidden now highlighted in red. Finally saving that object then displays it with some fields (but not all) missing.
It's seems utterly random.
I have added the following to my buildout:
extends =
base.cfg
versions.cfg
http://good-py.appspot.com/release/dexterity/1.0.3?plone=4.1
...
eggs =
...
plone.app.dexterity
My Plone is:
Plone 4111
CMF 2.2.4
Zope 2.13.8
The event.log doesn't have any messages in it when these problem are occuring.
Any insights appreciated.
Do you have a caching server in front of Plone? Maybe that is being too agressive and it is caching stale content. Try accessing Plone directly without any caching servers in between and see if that helps.