WordProof

Hi, glad you were able to resolve the issue! ??

Hi,

Thanks for getting back to us.

• I explained that the button should work, and specifically asked you to send me any error message if you encountered one. This helps us tremendously when tracking down the issue. I never dismissed your statement that it didn’t work, we believe you! For others (and us), the feature does work. Because of this, we ask for more information beyond “it doesn’t work”, which is what I replied to you. Again: feel free to provide us with more information, any error messages, or simply by stating that you’re not seeing any error message (which can be helpful in itself as well). We’d love to help.
• You can currently select post types to be timestamped automatically. We are working on adding support for categories in the new version of WordProof Timestamp, this feature is not ready yet.
• The bulk timestamp tool was added to the most recent version of the plugin — please update to the latest version and see if it works!
• I’m sorry you feel that way about our response — this is not how we intend our support to be experienced. I hope that you understand our position regarding requesting additional information when dealing with bug reports, it saves us and users a lot of time. I see you replied to my last response, so I’ll get back to your questions in our support tool. Thanks!

Jelle

Hi,

I’m sorry to hear that! I replied to your question one week ago, but haven’t heard from you since. I will resend that message, you should receive it in your email shortly. Can you confirm if you received it?

Regarding the demo: we are working on an update since it reflects an older plugin version. Since WordProof Timestamp 3.0, we have simplified the settings and moved many of them to my.wordproof.com. Please head there to change your settings, and please do get in touch if you need help. I’m not sure why you didn’t receive my reply, but let’s sort that out and get you set up!:)

Jelle

Hey!

We don’t have a list of known plugins that conflict with WordProof. Did you clear your cache?

Jelle

Hi,

Thanks for reaching out! We are working on an update (3.0.2) which will solve issue 1 and 3. Regarding issue 2: manually signing transactions with an EOS-based wallet will be re-added to the plugin in a later stage. It was not user friendly enough as of now, so we are rebuilding this at the moment.

Because we are in touch via Telegram, I will close this topic for now.

Thanks!

Jelle from WordProof

Hi both!

Thanks for updating the plugin to the latest version and for your engagement regarding the new features. We really appreciate it! I’d like to elaborate on our decision why we moved the settings from the WordPress dashboard to the My WordProof platform.

Before I continue: apologies from our side. Especially with such a big change, we should have communicated and implemented this change differently. We’ll try to do better in the future.

The main reason why we decided to move the settings from the plugin to make WordProof more universal for different platforms. It is our mission to enable all websites to incorporate transparancy and accountability, and to this end we are working on plugins for different CMSes (such as Shopify and Drupal). By moving the settings to My WordProof, we created a universal and modular SDK that can be used for other CMSes, e-commerce platforms, partnerships – as well as websites built with custom software who have implemented the WordProof API.

From a UI/UX perspective, I understand that this change is currently does not work well for WordPress websites. Because of your feedback, we just released a new update (3.0.1) which adds a WordProof page under the settings menu. From here, you will be able to open the settings modal (no new tab needed) where you will be logged in automatically. Thanks for your feedback!

I’m eager to hear further feedback, so if you’d be willing to test the new settings modal, please let me know what you think. We genuinely believe this is the right way forward for us, helping us cover as many CMSes as possible with our small but dedicated team. We will publish a release post later this week where I will elaborate some more on why we moved the settings to a pop-up modal. I do apologise for this sudden and undocumented change, we’ll try to communicate better in the future.

Thanks!

Jelle van der Schoot
Head of Product | WordProof.com`

Hey,

Apologies for the delayed response. The Copyright Infringement Claim Tool is currently in development and is expected to launch in March or April at the latest. I hope this helps; feel free to reach out via support if you have any other questions!:)

Kind regards,

Jelle from WordProof

Hey 1timebox,

Apologies from our side – this is not how we want people to experience our support service. Although I can’t see your email address / username, I expect to have found your ticket in our support system. Did you just receive a reply?:)

And thanks for the feedback, it helps.

Have a great day,

Jelle // WordProof

Hi Wilfredo,

Sorry to hear you still have problems with our plugin. At this moment, we cannot quickly fix the problem for you. Adding JSON-LD manually to your body won’t play nicely with the generated WordProof schema.

As I can’t offer a solution right now, I do have an alternative. The preferred way of adding JSON-LD is in the head of a page. Yoast SEO, for example, contains an HowTo Gutenberg block that adds the JSON-LD in the head and won’t cause any problems with WordProof. If you have the Yoast SEO plugin installed already, you do not have to install anything else.

Have this helps.

Marijn

Hey Wsan,

I’m sorry for the delayed response – my bad.

Regarding the issue: our devs weren’t able to find the cause of this issue and had a mixed success rate when it came to reproducing it, but I have just created another ticket and it will be investigated again. I’ll keep you better informed this time.

Jelle from WordProof

Hey Robert,

Quick update: the new certificate is almost finished and will reduce the loading time significantly. We expect to roll it out in June. I’ll close this topic for now, feel free to open a new topic / send us an email ([email protected]) in case you have any other questions or remarks!

Jelle from WordProof

Hey Miro,

Thanks for getting in touch.

The certificate link is added using default WordPress hooks which are recommended by WordPress. Some plugins use their own implementation, which causes other plugins (such as WordProof Timestamp) not to integrate properly.. I recommend you to contact the plugin author to solve this issue, as we don’t do custom third party plugin support. Sorry!

Jelle from WordProof

Hey, sorry for the delayed response!

1. Every site in your multisite network needs a new key, and thus counts as one website.

2. The only code that will run in that case, is the check whether the certificate link should be shown. Other than that, nothing is executed.

I hope this helps! Let me know if you have any other questions:)

Kind regards,

Jelle from WordProof

Hi Wsan,

We mark tickets as resolved as soon as they switch over to email to keep things organized, otherwise we have to keep track of the latest status in two places. Hope that makes sense! Our developers have started to investigate this issue, but we haven’t been able to replicate it. However, since you have experienced it on two different websites, we do think it has something to do with the plugin itself. We will keep you updated of any developments via email – sorry for the inconvenience!

Kind regards,

Jelle from WordProof

Hi Wsan,

I will close this topic to keep things organized – let’s continue this conversation via email so we can dig deeper into the issue!

Kind regards,

Jelle | WordProof