[gassho]

So you’re going to make a theme-wide decision based on one user, in this case me? Someone else is going to run into this. Such an unprofessional approach. Just because you can code doesn’t mean you are professionals. Omissions like this blockquote bug, bad customer service and support tell me this is an unprofessional theme house. I gave you the benefit of the doubt for a long time, but now I can’t tolerate it.

Manually double spacing paragraph breaks in blockquote doesn’t work for email and RSS subscribers — it renders as two spaces, not the workaround that works on the blog itself!

[gassho]

Thanks. I know what the <p> and <br> tags are an do! What I don’t understand is how this relates to the broken way your theme renders paragraph breaks in a blockquote!

And what’s further unclear is how these tags relate to when you FINALLY fix this in the next update, or if I start using the custom CSS you provided before.

In the Edit Post window I use the Visual composing text option. I hit ENTER button twice to get normal paragraph breaks when using blockquote. I don’t have the time to also look at the Text option when composing to see what hitting ENTER twice does to tags. Apparently is adds a <p> tag. So what? Do you really expect me to toggle back and forth on every post I write between Visual and Text to fix this error in the theme?!

Your theme should never been released in the first place with this error. As a result, whenever you finally decide to fix it in a new update, or if I use the custom CSS all my old posts have DOUBLE paragraph breaks because I already manually created an extra break to fix your error.

I tried the custom CSS. It works great on a new post, but it created DOUBLE breaks in ALL my old posts. That’s also what I don’t understand in relation to <p> and <br>. Is there a way to avoid this issue?

[gassho]

I’ve no idea what this means. There’s a language barrier here. Not being fluent in another language is not a crime, but if you’re going to be in the global theme marketplace based on WordPress which is predominantly an English language based platform, then please have techs who have a better command of English respond to this forum and support requests. Thanks!

[gassho]

So basically you’re telling me that something I reported in July of 2013 was not included in any of the updates since then, including this very last update! Why are we paying for this theme?! Here’s my original post:

https://www.themehorse.com/support-forum/topic/blockquote-will-not-retain-enter-line-space/

And when it is included in the next update, does that mean ALL prior posts are going to have DOUBLE paragraph breaks? And we’re going to have to manually delete all extra spaces from all old posts?

Your design/coding team needs a much better to-do list and work flow organization.

[gassho]

It’s reikihelp.com/blog

[gassho]

Thanks but there are 2 big problems with this:

Why didn’t anyone give me this custom CSS a VERY long time ago when I pointed out how blockquotes don’t render proper paragraph breaks?! I noticed that a long, long time ago. At that time I was told that it would be included in a theme update.

So now when I use this code it creates DOUBLE paragraph breaks in ALL my old posts!!!

Is there a way to make the custom CSS date-specific, for example it applies ONLY to new posts after the code is inserted?

[gassho]

The handling of this well-known vulnerability by Theme Horse has been horrible, especially for a premium theme. Today’s email announcing an update to the theme is the first and only one I’ve ever received! There have been posts here about why we don’t see theme update notifications in our WordPress dashboard as well.

Theme Horse has been very irresponsible in NOT letting all of its paid users know what exactly was going on, dating back to Sept 2014 at the very least. I just went through several weeks of stress, waste of time and expense in cleaning up my blog from a malicious hack exploiting what the whole tech world knows as Revolution Slider’s gaping vulnerability.

A very long time ago I tried to delete this plugin but it doesn’t or didn’t back then delete like a normal plugin. When I contacted the plugins author I was told that if baked into the theme, it can’t be deleted.

Theme Horse REALLY should have let us know MORE THAN ONCE, made a concerted effort to have us update our theme. Moving forward, why bundle anything in the theme at all?! Especially a shady plugin like this? WHY?

[gassho]

No, I took zero actions in regards to these warnings. ZERO. It fixed itself. And that was my point; all this backend stuff eats our time often for no good reason, when we need to be focusing on content! Any way, I’m glad I have a clean dashboard now.

As for this forum, today to post this I didn’t have problems. When I posted the last comment, there were a lot of problems. We’ll see what happens next time…

[gassho]

Since I started this thread, let me add today that over the last few days the warnings for my blog simply dissappeared. I did NOT update my theme. Warnings appeared after WordPress updated to 4.0. Then we went through all this on the forum and now I have a warning-free dashboard. I’m really over WordPress updating so much and breaking themes. I’m also really over this forum and the supposedly pro theme’s website being broken all the time, and super slow. In emails with support they recently said they changed their hosing environment. Today trying to post this, I got several database errors before being able to login to post.

Oh the joys of running a blog these days!

[gassho]

Personally, I’m not removing anything until I hear from Theme Horse officially. Didn’t this hack break someone’s blog on your other thread about it? Plus, doesn’t it have a reason for being there, so if you remove it… Catch my meaning? Where is Theme Horse, by the way? They’re always too busy cranking out new themes instead of attending to the customers they already have. They posted a couple of times here to email them a temporary username and password but I’m not comfortable with that and since this is theme-wide they need to handle it differently.

[gassho]

As for editing posts (haven’t posted anything new since the warnings started), I’m able to edit and my blog is live, the public can see it. What happens when I edit a post and click update is it retains the edit, but the post edit screen disappears, and these warnings show up. All warnings are in /wp-content/themes/attitude-pro/ so it’s definitely an issue with the theme!

Warning: simplexml_load_string(): Entity: line 1: parser error : Space required after the Public Identifier in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): Entity: line 1: parser error : SystemLiteral ” or ‘ expected in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): Entity: line 1: parser error : SYSTEM or PUBLIC, the URI is missing in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: Cannot modify header information – headers already sent by (output started at /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php:123) in /home/reikihel/public_html/blog/wp-admin/post.php on line 233

Warning: Cannot modify header information – headers already sent by (output started at /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php:123) in /home/reikihel/public_html/blog/wp-includes/pluggable.php on line 1173

[gassho]

We shouldn’t have to let you in to our WP dashboard. Creating UN/PW is time-consuming!!! This is happening for everyone using this theme with the new WP 4.0 update. We’ve provided the warnings (see above and pasted below and other threads here). It’s across the board. Figure it out from the warnings we’re posting and fix it.

Yesterday all my warnings were gone. Today they’re back but there are less of them. This is what I see in my dashboard:

Warning: simplexml_load_string(): Entity: line 1: parser error : Space required after the Public Identifier in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): Entity: line 1: parser error : SystemLiteral ” or ‘ expected in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): Entity: line 1: parser error : SYSTEM or PUBLIC, the URI is missing in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

Warning: simplexml_load_string(): ^ in /home/reikihel/public_html/blog/wp-content/themes/attitude-pro/library/functions/update_notifier.php on line 123

[gassho]

I’ve the same warnings. These are warnings, not errors. I’m going to start a new thread. All these warnings are in /wp-content/themes/attitude-pro/, meaning they are programming problems in the code for the theme. Seems like Theme Horse needs to change some coding to make Attitude Pro work better with WordPress 4.0

[gassho]

I am not getting notifications of replies to my email. I am subscribed. Checking here all the time is very inconvenient.

[gassho]

I’m subscribed but there was no email letting me know someone replied. It’s an “area” or box with author bio, social links, etc. It can be on post permalinks, pages, etc. It can be at the top of a post or below. It grabs the info you have in the user section of WP. It’s very useful for multi-author blogs, but also for single-author. I used a plugin for the time being, but was wondering if this theme has a way to include it without a plugin. Plugins make the user info more robust. Here’s an example from one of my posts:

http://reikihelp.com/blog/2014/01/peace/

[Author]

Posts