Ervin Domonkos

Thanks for taking the time to read it.

I really appreciate it.

Hi @karmatosed,

Yes, the link was here, but it was removed by the moderators.

Adding back again, hopefully the next mod will read your post and won’t ban me from here for adding my link again…

Here you go:
(Link removed again. Stop.)

(alternatively, I can send the link to your email or Twitter if the link can’t stay here)

• This reply was modified 6 years, 3 months ago by Samuel Wood (Otto). Reason: Don't post links, post full reviews

Yes, it was a focus bug. Actually I couldn’t click on the title line because the toolbar for content was always visible.

However, I was able to focus to title using SHIFT+TAB.

Looking forward to the next version.

• This reply was modified 6 years, 4 months ago by Ervin Domonkos.

Hi Tobias,

Thanks for the quick answer, especially on a Sunday afternoon, I appreciate it.

Yes, finally I found the very same solution as the workaround that you proposed. It works fine with the on-page links (that I was really looking for). However, as I am building a glossary-like page with TablePress, it makes it a bit less readable in admin.

This is not a big problem though at the moment, so your workaround will work fine for now.

Thanks,
Ervin

Hi martijnbalink,

I’m terribly sorry, I’ve just seen your support ticket here. I am happy that you were able to resolve this issue.

Anyway, if you read this message, I would be really happy to know why it didn’t fit your requirements. We are constantly collecting ideas how to make our plugins better.

Thanks,
Ervin

Yep, it was my bad. When changed the brand name in all files recently, I bulk replaced all strings, including the Contributors part and somehow didn’t notice when uploading that it should’ve been the username.
Thanks for pointing me in the right direction.

• This reply was modified 8 years, 1 month ago by Ervin Domonkos.

Thanks for the quick answers!

I’ll update the other plugin soon, so I’ll check what happens after the Author line in the readme is updated.

About the display name: yes, it’s obvious that the system should respect my username instead my display name. Simply I bumped into situations when I had to make the same settings again and again.

However, I’ll check if the issue gets fixed after I made the Author line the same in both readme files, and will update this topic afterwards.

I’ve just released a new version (0.3.1) with 2 bugfixes, hopefully it will resolve your issues, too.

Please let me know if your problem is different.

Hi Bas,

Just tested it with WP 4.6 and it works flawlessly on my system. Could you please explain the issue to me in more details?

What is not working and how did it work before you upgraded it to 4.6?

Hi, thanks for flagging this up, I’ll test it in a few hours.
Will get back to you soon!

Didn’t forget about it, the next version will be out in a few days…

Hi Phil,

According to the FAQ, the SOAP extension has to be enabled in php.ini. Is the following line present in your php.ini file?

extension=php_soap.dll

Cheers,
Ervin

I know how I can change it, it’s not the question.

My question is: why is WordPress the default value here, why not the site name (that’s stored in General settings)?

I think having the site name as default can make your plugin easier to use because of 2 reasons:

1. I doubt if anybody would want to send emails to his/her clients in the name of “WordPress”…

2. Most of the users of your plugin will change this default value to their site’s name (with the method you shared above)

This way you would save some time for the most of your users.

Now the journey is:
1. Hey, I need the Mail 2 function, too.
2. Let’s use my email address there…
3. OK, let’s try if it works…
4. Yeah, I got the mail!
5. WTF? Why is WordPress the sender?
6. Search for the solution on Google
7. Found this: Mail that comes through the contact form shows “WordPress” as its sender name. How can I change this?
8. Change the From: field again
9. Test it
10. Yeah! It works

The new journey would be:
1. Hey, I need the Mail 2 function, too.
2. Let’s use my email address there…
3. OK, let’s try if it works…
4. Yeah! It works

More usable, I think…

I mean, if you are not using use the

[your-name] <[your-email]>

format, only

[your-email]

It will add “WordPress” as the sender’s name.

I think there was a change in the wpdb::prepare() function: in earlier WP versions the 2nd argument was optional, and from 3.5 it became obligatory. That’s why it gives you that error message.

This way, all the plugin developers who use the prepare() function and did not use its 2nd argument will have to make some tiny changes to their plugins…