# WP Discourse 1.0.0 release

**URL:** <https://meta.discourse.org/t/wp-discourse-1-0-0-release/50753>\
**Category:** Extras\
**Tags:** wordpress\
**Created:** [Septembre 27, 2016, 8:10 UTC](https://meta.discourse.org/t/wp-discourse-1-0-0-release/50753 "2016-09-27T20:10:08Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon)\
**Post date:** [Octobre 11, 2016, 6:54 UTC](https://meta.discourse.org/t/wp-discourse-1-0-0-release/50753/3 "2016-10-11T18:54:51Z")

</div>

I will fix both those issues in the next update, later this week.

Edit: I’ll try to get it done today.

The `datetime` issue has, hopefully, been fixed in version 1.0.2. Let me know if it isn’t working.

> [@heptoilabas](#):
>
> There is another little word that isn’t in the translation part of the plugin, the “says”,

That word is only supposed to be available to screen-readers. It is in a span that has the `'says'` class applied to it. In the default WordPress theme’s css, that class has this rule:

```plaintext
/* Text meant only for screen readers */
.says,
.screen-reader-text {
	clip: rect(1px, 1px, 1px, 1px);
	height: 1px;
	overflow: hidden;
	position: absolute !important;
	width: 1px;
	/* many screen reader and browser combinations announce broken words as they would appear visually */
	word-wrap: normal !important;
}

```

It seems that using the class `'.screen-reader-text'` is a more standard way to do it. I’ve added that class to the span, and also internationalized the word. If it is still showing up in your theme and you don’t want it there, try adding the above css to your theme’s css.

---

_[View the full topic](https://meta.discourse.org/t/wp-discourse-1-0-0-release/50753)._