Vitor Madeira

This is so wrong…

Let’s all go to the biggest shop doors and forbid them to sell knives.

You know? Knives kill people… Oh wait, people kill people… With knives…

So who’s the fault? Is it the knife maker, the seller or the one who actually kills someone?

To make it a bit short: The plugin directory is supposed to let people get here and have a right to choose, right?

One should suppose that people who runs selfhosted WordPress websites should know what they are doing.

Oh no… You see, I need this plugin, but you don’t want it to be available, so I must not have the right to have it available, because you don’t want to.

People here need to become a bit more neutral.

If you don’t want to use the plugin, don’t.

I would agree with you if a “WARNING” sign (and description) should be added on the plugin’s main page, but a bad rating ‘just because’, I feel it’s just not right.

Hi!

If you use a commercial theme or plugin and need support, please go to their official support channel. In order to be good stewards of the WordPress community, and encourage innovation and progress, we feel it’s important to direct people to those official locations.

In your case, I suppose this would be the correct place to get appropriate help:
https://www.gravityhelp.com/support/

Forum volunteers are also not given access to commercial products, so they would not know why your commercial theme or plugin is not working properly. This is one other reason why volunteers forward you to the commercial product’s vendors. The vendors are responsible for supporting their commercial product.

Is there only restriced access to this team?

You can learn how to access the WordPress Slack in here:

Slack

Hope it helps.

• This reply was modified 7 years, 10 months ago by Vitor Madeira. Reason: Typo on my text

Hi, I’m no specialist on coding so I’m not definitely the most skilled guy to help you, but I’ve just found another clue that might help someone a bit more skilled than me helping you.

I just found that all the locales for the latest version of that plugin are showing has having 0 (zero) strings for translation:
https://translate.www.ads-software.com/projects/wp-plugins/blog2social/dev

But the previous version seems to be okay:
https://translate.www.ads-software.com/projects/wp-plugins/blog2social/stable

So that, in my opinion, might have got to do with your source code files. Something might have gone wrong that changed the source code files from the prior version onto this last one.

Please allow me this question: Are you the authors of the Plugin? Your username seems t have something related to this plugin, right?
You might want to talk to your coding developers and try to check with them that might have been changed in the source code that might be causing this behaviour on the plugin translation functionality.

Or… One should consider the other half as well and try to contact the GlotPress team and ask some questions and try to understand if this would be something that might be happening on their side.

There is a group dedicated to GlotPress stuff in WordPress Slack. I will try to get some attention from there, as someone might be able to help you better than me.

Hope you find the solution for your problem soon.

Hey! Let me be the one giving you a big thank you for taking the time to get back here, editing your post and teach us all how you got around your problem.

That should be the way to do it for every one of us who enjoys participating in this fantastic community, run by voluntary spare time.

Keep it up!

Good to hear that you’ve got your problem solved.

I’ve been using uBlock for quite some time and have no problems at all…
I mean, in the beginning, yeah, it was like a shark (eating everything that moved…) but then you learn a bit how to use filters and stuff, and everything gets okay.

But anyway, I guess it would be a good idea to try tweaking around it for a bit and/or install some other adblocker, if you really need to.

It sure was a pleasure being able to help a bit.

Are you still facing this problem?

I don’t speak polish but I saw the “AMP” string available for translation and translated it with no problems.

I also made a lot of translation suggestions on the Portuguese (Portugal) locale and found no errors. (https://translate.www.ads-software.com/locale/pt/default/wp-plugins/sassy-social-share)

You might want to try deleting your browser’s temporary files and/or cookies. or try using a different browser?

Hope you find the solution soon.

• This reply was modified 7 years, 10 months ago by Vitor Madeira. Reason: Typo on my text

When does the problem occurs? Is it only when you try to import POEdit files, or does it happens also when you try to translate inside GlotPress website?

I’m not that expert, but it seems that some German strings do not seem to be 100% accurate.
Take this string, for example, it is showing as being translated, but it is a copy of the original English string… How did that happened?
https://translate.www.ads-software.com/projects/wp-plugins/blog2social/dev-readme/de/default?filters%5Btranslation_id%5D=49728127

hummm…

Well, this is really odd… (It seems to be quite some problem there…)

When I go to my own locale (Portuguese from Portugal), I get no strings available for translation in Development (trunk).
https://translate.www.ads-software.com/projects/wp-plugins/blog2social/dev/pt/default

Please, let me suppose something different here. I guess that, for this kind of thing to be happening, it seems that someone might have changed the code on the newest version of the source code and might have made the strings unavailable for translation. Would you consider this idea, or it does not apply to your case?
https://translate.www.ads-software.com/locale/pt/default/wp-plugins/blog2social

It also could be something related to the GlotPress site functionality itself?

Hi there.

Your idea is quite nice: It would be just perfect to have a date field showing in our WordPress Plugins Panel that would allow us to better understand what plugins might be “in danger” considering that old and unmaintained code is a serious security flaw, right?

I guess I might have found a plugin that would be of quite some help on your quest:
https://www.ads-software.com/plugins/vendi-abandoned-plugin-check/

Give it a try and see if it helps.

Oh, that was odd…

Anyway, I just found this information that might be useful for you, as it would be of extreme priority to have the latest version due to some vulnerabilities found on the old versions. Please give it a good read as I guess it might help you somehow:
https://www.ads-software.com/support/topic/read-this-first-wordpress-4-7-master-list/#post-8521428

I don’t know if you already got your problem solved, but it sounds like it might be a cookies / browser temporary files problem.

Have you tried clearing cookies / temporary files on your browser?

Have you tried on a different browser / different PC?

Check if you have the latest version of the browser.

Also, do you have any kind of browser add-on that might be blocking JavaScript and/or some other browser elements?

(probably, the cleaning of temporary files might help, I guess…)

Some themes do not support the “featured images” option, so that could be one of the possible the reasons why it did not went well after the export.

Also, I guess you should ask for help in the WordPress.com support forums, as it seems that it is something that they would be gladly willing to help, right?

Hope it helps.

Have you tried doing the same using another host, or even on localhost – on your local computer?

Given the fact that there isn’t much info to try go any further, I would say it would be a good idea to try doing the same, but with a different hosting environment.

Using XAMPP (you can install it in Linux or Windows, where there is even a Portable version available, so it makes it even easier to setup) it would be nice starting point to try understand if the problem would persist or if it would remain.

Hope it might help you a bit…

Hi. Have you already solved the problem?

If not, what web browser are you using?
Have you tried deleting all cache and temporary files on your browser?
Have you tried using a different web browser?

Hi. Does the problem still persists? I visited your URL and I see a youtu.be link, so I guess you might have edited the comment? (I can’t seem to see any layout problem on that page)

Was it something related to a theme you were using?