Reply to: tickets(179961)

Hi Michael,

You might be but noone else requested that to us previously, so this must not be an error from everyone.

Reply to: tickets(179404)

Hey Craig,

Thank you for your feedback, it is much appreciated.

Yes you are correct this is the best-case scenario. We have forward the request as a feature request so we might be able to add the PO files inside also, so translations can happen.

We have worked on the Settings page, so it is easier for our users. Maybe the PO based translations will not be possible, but we might have the opportunity to generate translations based on a JSON file that you can import to the settings and everything works properly for sharing translation files this way.

We will do let u know if we have anything related to that as an update.

Reply to: tickets(179964)

Hey Michael,

I am not sure, I do think that those are basically based on what type of web site you have submitted to google and then google scans the web site based on schema + property type.

I do not think you should spend any time on that, it is clear that it is not something to waste time on.

Reply to: tickets(179228)

Hi Craig,

We are sorry for the delay.

I have changed the priority of the task so he can check that quicker for you.

We appreciate the patience

Reply to: tickets(179404)

Sure it is “very easy”, but this is true for most plugin, but they still provid language files as a service to their customers. There are many reasons for this:

  • It provides consistent translations. Those who are skilled in translating in the user base can provid translations that the entire community benefits from.
  • It takes time to translate and it seems extremely unnecessary for everyone to do it rather than pooling resources.

I don’t understand why you don’t follow best practice in this and do what pretty much all other providers of WordPress plugins do and maintain language resource files for different languages.

Reply to: tickets(179964)

Hi Basilis,

 

I’m interested to understand the warning and find out the reason for that. What are this fields related to? Is there a field I need to fill in to make it go away?

Reply to: tickets(179961)

Hi Basilis,

I’m actually not using the Visual Composer, I’m using the Text Composer. Even if I delete everything, I do get the error.

 

 

 

I dont think this is a customization request as I’m probably not the only one who has that issue and it will affect google ratings.