The problem is for the website https://ukupdates.co.uk for some reason I cannot get the images to work correctly with facebook.
When using the debug tool I get this showing in the warning...
Extraneous Property
Objects of this type do not allow properties named 'og:title'.
I have tried many different plugins to create the meta tags and none work so don't think that is the issue. In terms of plugins installed I have AMP, Autoptimize, Short pixel image optimizer ive tried de activating these but nothing seems to solve the problem.
https://developers.facebook.com/tools/debug/echo/?q=https%3A%2F%2Fukupdates.co.uk%2Frare-full-moon-happening-on-friday-the-13th-for-the-first-time-in-20-years%2F
Extraneous Property Objects of this type do not allow properties named
'og:image:width'. Extraneous Property Objects of this type do not
allow properties named 'og:image:height'. Extraneous Property Objects
of this type do not allow properties named 'og:image:alt'. Extraneous
Property Objects of this type do not allow properties named
'og:description'. Extraneous Property Objects of this type do not
allow properties named 'og:type'. Extraneous Property Objects of this
type do not allow properties named 'og:title'. Extraneous Property
Objects of this type do not allow properties named 'og:url'.
Extraneous Property Objects of this type do not allow properties named
'og:updated_time'. Extraneous Property Objects of this type do not
allow properties named 'article:tag'. Extraneous Property Objects of
this type do not allow properties named 'article:published_time'.
Extraneous Property Objects of this type do not allow properties named
'article:modified_time'. Extraneous Property Objects of this type do
not allow properties named 'article:author'. Extraneous Property
Objects of this type do not allow properties named 'article:section'.
Extraneous Property Objects of this type do not allow properties named
'twitter:card'. Extraneous Property Objects of this type do not allow
properties named 'twitter:title'. Extraneous Property Objects of this
type do not allow properties named 'twitter:description'. Extraneous
Property Objects of this type do not allow properties named
'twitter:image:width'. Extraneous Property Objects of this type do not
allow properties named 'twitter:image:height'. Extraneous Property
Objects of this type do not allow properties named
'twitter:image:alt'. Extraneous Property Objects of this type do not
allow properties named 'twitter:url'. Extraneous Property Objects of
this type do not allow properties named 'profile:first_name'.
Extraneous Property Objects of this type do not allow properties named
'profile:last_name'. Extraneous Property Objects of this type do not
allow properties named 'profile:username'. Share App ID Missing The
'fb:app_id' property should be explicitly provided, Specify the app ID
so that stories shared to Facebook will be properly attributed to the
app. Alternatively, app_id can be set in url when open the share
dialog. og:image could not be downloaded or is too small og:image was
not defined, could not be downloaded or was not big enough. Please
define a chosen image using the og:image metatag, and use an image
that's at least 200x200px and is accessible from Faceboo... See More
Parser Mismatched Metadata 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... See More
Related
I would like to dynamically set the path of the sql file in the code below using parameters.
files:
/tmp/setup.mysql:
content: !Sub |
CREATE DATABASE ${DBName};
CREATE USER '${DBUsername}'#'localhost' IDENTIFIED BY '${DBPassword}';
GRANT ALL ON ${DBName}.* TO '${DBUsername}'#'localhost';
FLUSH PRIVILEGES;
mode: "000644"
owner: "root"
group: "root"
I have tried simplistically adding a Reference to a custom Path parameters but, unfortunately, I am getting the following error from the Template Designer.
Template contains errors.: Template format error: [/Resources/MyLaunchConfig/Metadata/AWS::CloudFormation::Init/config/files] map keys must be strings; received a map instead
How can I move a path like this into the template parameters?
Edit:
The Note on the CloudFormation documentation on Intrinsic functions says the following:
You can use intrinsic functions only in specific parts of a template.
Currently, you can use intrinsic functions in resource properties,
outputs, metadata attributes, and update policy attributes. You can
also use intrinsic functions to conditionally create stack resources.
This seems to indicate that the functions should be available in resource properties and metadata attributes. It does not specifically restrict it to the values in these objects rather than the keys (although this could be assumed by the inherent nature of keys vs values).
Based on the comments.
The issue is that according to the CFN format specification, a map can only be string:
A map is a collection of key-value pairs, where the keys are always strings.
Therefore, a proposed solution was to use UserData to define the dynamically generate file, instead of using CFN metadata.
I need to pass a custom object from one fragment to another fragment. I use androidx navigation for navigation between fragments. I had to use deepLink for navigation for my use case.
The navigation graph with the destination fragment has,
<fragment
android:id="#+id/ListFragment"
android:name="com.joseph.learning.ListFragment"
android:label="ListFragment">
<argument android:name="todoItem"
app:argType="com.joseph.learning.models.todoItem" />
<deepLink app:uri="android-app://androidx.navigation/todoList/{todoItem}" />
</fragment>
And from the source fragment, the navigation is initiated like
findNavController().navigate(
Uri.parse("android-app://androidx.navigation/todoList/$item"),
NavOptions.Builder()
.setEnterAnim(R.anim.transition_slide_in_right)
.setExitAnim(R.anim.transition_slide_out_left)
.setPopExitAnim(R.anim.transition_slide_out_right)
.setPopEnterAnim(R.anim.transition_slide_in_left)
.build()
)
But this fails as soon as it executes with below error
java.lang.UnsupportedOperationException: Parcelables don't support default values.
at androidx.navigation.NavType$ParcelableType.parseValue(NavType.java:679)
at androidx.navigation.NavType.parseAndPut(NavType.java:96)
at androidx.navigation.NavDeepLink.parseArgument(NavDeepLink.java:306)
...
If incase, the custom object as argument is replaced with string or integer, then the navigation works without any issues. Also the passed data can be extracted in the destination fragment using navArgs()
What should be done to pass custom object across fragments ?
Android Documentation
Routes, deep links, and URIs with their arguments can be parsed from strings. This is not possible using custom data types such as Parcelables and Serializables as seen in the above table.
Solution: To pass around custom complex data, store the data elsewhere such as a ViewModel or database and only pass an identifier while navigating; then retrieve the data in the new location after navigation has concluded.
When i create a property element in WSO2 ESB it allows me to create without the "type" attribute being mentioned like
However while using the WSO2 developer studio to generate the property in one of the sequences it kind of mandates the 'type' attribute to be present . Is there an option to override it.
i tried removing the attribute in source view and tried saving it . But it overrides and invoked the attribute during save.
The attribute 'type' is mandatory in developer studio. If you are creating the sequence through the design view and you didn't define type it will consider as String by default.
If you are creating the sequence through the source view and you didn't define type or remove the type and save it will consider as OMElement by default.
I can find the classes a WMI host supports using a WQL query of
SELECT * FROM meta_class
This returns the classes and their methods and properties. These seem to be all strings. I'm trying to do some discovery and while having the property names is nice, getting the types of the properties would be even better. Is it possible to get the types of the properties?
For example, if the above query returns the class CIM_Processor with a property of Family can I tell that Family is a uint16 rather than say a uint32 or a string?
I've been reading through Retrieving Class Definitions but can't seem to find a query that returns types. Is this even possible? Is there a workaround not using WQL?
I'm not aware of the existence of a WMI class which retrieves the properties types. But you can enumerate the properties of a WMI class using the SWbemPropertySet object and then access each property of the collection( SWbemProperty) and read the value of the SWbemProperty.CIMType property. If you are using .Net you can access the same information using the PropertyData Class and the Type Property.
I'm using POCO to auto generate my entities from DAL project to Entities project. I currently have no need in creating view classes manually.
However I have one problem - When I try to return a poco object that has navigation properties from a [WebMethod] I get the following error:
Cannot serialize member Entities.City.Customers of type System.Collections.Generic.ICollection1[[Entities.Customer, Entities, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]] because it is an interface.
I tried writing context.ContextOptions.LazyLoadingEnabled = false; and
context.ContextOptions.ProxyCreationEnabled = false; to no avail.
if I add [System.Xml.Serialization.XmlIgnore] before the properties, I get no error, but then I lose those properties?
The message is clear: serialization fails because your Entities.City.Customers member is declared as an interface (ICollection).
The interface does not say anything about the implementing type, it only defines the contract that the implementation should follow. As such, the serializer does not know how to represent the implementation in a serialized format.
You might think that it's not that hard to reflect the type and serialize based on the information you get from introspection, but the problem will be when you try to deserialize from this representation. The same representation could possibly correspond to all implementation types, in which case what should the serializer choose as the concrete type?
There are a few steps to work around this limitation, as you can find in this post: XML serialization of interface property. In your particular case, the simplest way would be to make the Entities.City.Customers member of a concrete type like List<Customer> instead of ICollection<Customer>.