Halo Diehard

I have tested registration using Social Login this morning, and in my Users list it doesn’t say anything below Registration (the new column in my Users page after following your instructions to show which social network was used to log in). So I can’t verify if the fake accounts used Social Login that way. I used the Windows Live login option for the test.

So I realized I might get a clue looking in my deleted email notifications. There weren’t many that hadn’t be deleted permanently, but I see two other recent members who I’ve kept on (assumed they weren’t fake users), who also registered using Windows Live (their registrations also do not show under the new column as registering via Windows Live, it’s just a blank column).

So the column doesn’t appear to be functioning correctly and telling me whether or not users are signing up using Social Login, but it’s looking like you are correct and perhaps they are not. Moving forward, I’ll have to pay attention to the email notifications to tell. Will report back if I start getting emails notifying me they’re signing up with Social Login. If I do not, apologies for my assumption!

Hello, and thank you for your quick response! I have followed your instructions and then re-enabled registration on my site. I will report back after the first handful of registrations. (I’d already deleted all the fake accounts)

• This reply was modified 5 years, 1 month ago by Halo Diehard.

HAHAHAHAHAHA! You’re hilarious. I’m not doing that. I have never, ever had any theme or plugin SPAM my WordPress admin pages like your theme is doing. It’s inappropriate. I will be removing your theme.

For anyone else who runs into this issue and finds this thread:

It turns out that for some reason, my WordPress site was no longer paying attention to my php.ini and wp-config.php files, which I had used to increase my memory years ago, and which had been working fine up until the fatal errors started a few days ago.

The fatal errors were solved by placing additional php.ini files in both the root and wp-content folders of my site, as well as in wp-admin (where WordPress users are instructed to place the php.ini, and where my existing file was).

For anyone not familiar with this code, a php.ini file is not included when you install WordPress, and you can create the file using a text editor, saving it as php.ini I have the following code pasted into all three php.ini files in the locations described above. It fixed all of my fatal errors, which were occurring on my forum page as well as in widgets, depending on what page I was on.

memory_limit = 512M;
max_input_vars = 5000;
post_max_size =256M;
max_file_uploads = 300M;
max_execution_time = 180;
max_input_time =120;
upload_max_filesize = 128M;

Hope this helps someone like it helped me!

• This reply was modified 5 years, 10 months ago by Halo Diehard.

Ok, so I had a brain storm and found a workaround for not being able to change what page I want my forums on in the Simple Press Integration settings. The page that refused to change was forum, and the page I wanted to use was forums (with the “s”). I put my page forums (with the “s”) in the trash, and edited forum to have the “s” on the title and slug, and it worked. Still, something is borked if I couldn’t just change it, but at least there’s a workaround.

Everything is now as it should be ??

• This reply was modified 5 years, 10 months ago by Halo Diehard. Reason: Marked resolved

Hello, Nigel, thank you for your speedy reply. Apologies for the multiple issues thread; it didn’t even occur to me I should open separate ones.

I have some good news! Somehow, my php.ini and wp-config files stopped increasing my website’s memory. Working with my host, they put a php.ini in my wp-content folder, which I’d never heard of doing. They also replaced my existing php.ini files to include the same exact code. For anyone experiencing similar issues, my host is Ionos, and the php.ini file has been placed into all three: my root, my wp-admin AND my wp-content with the following code:

memory_limit = 512M;
max_input_vars = 5000;
post_max_size =256M;
max_file_uploads = 300M;
max_execution_time = 180;
max_input_time =120;
upload_max_filesize = 128M;

This change has also fixed the Wise Chat shortcode issue: the chats now all show up as they are supposed to. And I found out later the post and reply buttons in Simple Press weren’t working, either, and this fixed that problem as well.

The one issue that remains is that I still cannot change my forum page in Integration. Any existing page I try to use changes back to “forum”.

If this were the case, I would have had problems previously to whatever updates has caused the conflict. Also, I don’t believe my PHP memory limit is 64MB, regardless of what the fatal error says. It’s already 128 in my wp-config, and I’m fairly certain I’ve double checked with my host in the past. Strangely enough, after a day of trying to problem solve this, I found if I swapped out a Simple Press forum theme with another theme, the issue resolved. The theme is called CSS-Only (if anyone else runs into this problem), so it’s confusing why it would cause a fatal error, but with the theme activated I could not run Yoast SEO at the same time as Wordfence, and then other fatal errors were showing up in my sidebar widgets for other plugins and files, but only on that forum page.

I just realized that Wise Chat is the plugin I am referring to above, who’s author believes the conflict lies with Simple Press and not his plugin. But neither Wise Chat nor Quick Chat will work. I have Simple Ajax Chat plugin shortcode on my forum page right now and it’s working, but I would prefer Wise Chat.

• This reply was modified 5 years, 10 months ago by Halo Diehard.

I just found info about the Health Check plugin, installed it and went through the plugins. Yoast SEO and Simple Press get along fine until Wordfence Security is activated, then I get two fatal errors:

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in …/wp-content/plugins/simplepress/forum/content/classes/sp-view-class-spcgroupview.php on line 82

Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 65536 bytes) in …/wp-content/plugins/wordpress-seo/admin/class-yoast-notification-center.php on line 497

Any and all help appreciated!

Yes, apologies, I thought I *was* clear. I do not want that advertisement banner constantly on every single one of my admin pages.

@nextscripts, awesome, thanks! Will do.

My review is based on your plugin vs all of the other plugins I’ve tried. Most top plugins don’t require users to go pro to get basic functionality. The options given with the free version of Social Warfare make it a waste of time to even try the plugin. I’m not interested in share counts or any other bells and whistles; I only need buttons for visitors to share information to the few basic top sites out there. That includes Facebook, Twitter, Google +, Reddit at the very least. Social Warfare is the only plugin I tried to not supply the top sites. If it’s meant as a “teaser” to push pro features, it’s a fail, because as quality goes the free version is shabby, and I would never trust the pro version to provide quality service when the free version is shabby, even if I was interested in paying for it. There are quality, free versions with a plethora of options, including different button image choices, and some even allow you to upload your own buttons. Free. Options to place buttons above and below content as well as pop up and fly in buttons. All free, and all with the top sites included.

@otto42 omg thank you so much for taking the time to throw all that my way. I knew most of it, but it was kind of a jumbled mess in my head. That point system really clarified it for me. Also, specificity! That is what I was referring to above when I was using the word “path”; I just didn’t know the correct terminology.

Thanks for clarifying how order works in CSS as well.

Your post is exactly what I was looking for to help me organize what I needed in my brain.

RE “odd” and “even” in HTML, I pulled that class example straight from bbpress code, lol, that’s not me. I know even less about HTML than I do CSS.

But yeah, great reference, man, I’m sure I’ll be referring back to your post in the future next time I get stuck!

I accomplished a fix to this by posting the following CSS into my child-theme’s CSS (which for anyone using the Matheson Theme can easily be done in Customizing view, Additional CSS)

.format-standard div.simplesocialbuttons.simplesocialbuttons-align-left {
     clear:right
}

Which brings me back to my original question: is there a set of rules to follow to correctly override a parent theme’s CSS with the child theme’s CSS, or is it mostly just mucking around until you figure it out?

I’m sure my not being familiar with the terminology isn’t helping me to clarify just what I am asking, but I will try.

I’m looking for guidance on how to determine the hierarchy “path” to the specific element who’s CSS you are looking to change. For example, here is the class of your post just above this one:

div#post-10918376.odd.bbp-parent-forum-21260.bbp-parent-topic-10918292.bbp-reply-position-5.user-id-7819546.post-10918376.reply.type-reply.status-publish.hentry.by-moderator.author-has-badge

It’s inheriting CSS from:

.bbpress #bbpress-forums li.bbp-body div.hentry

That is the “path” I am referring to. div.hentry is inside of li.bbp-body which is inside of #bbpress-forums, which is inside of .bbpress. Each div inherits it’s parent’s CSS unless it has it’s own CSS that overrides it.

My understanding is that in a CSS document, the CSS is read from top to bottom, with the rules being executed in that order, so rules beneath are higher priority in the hierarchy, this is why a child theme’s CSS is supposed to overrule a parent theme: because it is loaded after the parent theme’s. But herein lies the issue: the more specific a “path” to a CSS rule is, the more of a chance that it will have a higher priority in the heirarchy than a conflicting rule that is executed AFTER it.

Because of this, if I want to change a more specific element than can be accomplished by a simple copy/paste of my parent theme, I may need to be more specific in the “path” to my element.

For example, let’s say I wanted to change your moderator badge color, I could (theoretically) just paste this parent theme code into my child-theme’s CSS and change the color:

.author-badge-moderator {
     background-color: #000000;
}

But let’s say I only want odd row moderator posts to have a black moderator badge background. There isn’t a CSS rule for that in the parent theme, so maybe I would do something like this:

.odd .author-badge-moderator {
     background-color: #000000;
}

Problem is, that might not be specific enough of a “path” to overwrite any parent CSS that might conflict, so I might have to do:

.bbpress #bbpress-forums li.bbp-body div.hentry .odd .author-badge-moderator {
     background-color: #000000;
}

Thing is, that might not work either, which brings us right back to my original question of is there a basic set of rules that helps me figure out how to determine what “path” I need to use to override parent theme CSS.