davidschwartzer

Lap:

Thanks for the follow-up. I have been in touch with my hosting company support and they confirm there is a problem on the server but so far, haven’t been able to resolve it. I have asked about the Apache log files but haven’t gotten an answer about that either.

I’ll report back as soon as I hear more from them.

Regards,

David

Lap:

Thanks for your follow-up. I did look at my directory structure and see a folder called Logs and it has a lot of files in it but none that are labeled in a way that leads be to believe they are from the Apache server.

I tried to add the line to the .htaccess as you suggested but when I loaded it into the root of my Wordpree directory I could not launch my site and got this error message:

Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

I did change the name of the old file to .xxxhtaccess before I loaded the changed file. As soon as I removed the changed file and named the original file back to the proper name, I again got access to my site.

Any other thoughts?

Regards,

David

Lap:

Thanks for your response. Can you provide some guidance on where to look for the Apache log files? I’m not sure my hosting company gives me access to that part of the directory but I can look if you can point me in the right direction.

Regards,

David

Dear Thecus:

We are Apple Tech Talk (https://appletechtalk.com). A web site that focuses on technology for and compatible with the Apple platforms.?

Although there are many web sites available that discuss Apple and its technologies in a broad sense, and other sites that look at product reviews with?just a passing thought about Apple compatibility, we think we are unique by focusing on the products that are not only made by and for Apple, but also all the other great products that work with Apple technologies.

We are not a rumors site, and you won’t find us reporting on the lines that form outside Apple stores, days before a new product launch. ?Our goal is to provide in-depth, but easy to understand reviews of products and services that are not only made specifically for Apple products but are also compatible with Apple products. Whether its hardware or software, desktop or mobile, we’re here to “kick the tires” and see what it can do.

Even though Apple Tech Talk is fairly new, our site already received hundreds of views each day from readers around the world.

We are currently doing a comprehensive series on Network Attached Storage (“NAS”) for home and SOHO users, and some of your competitors have already provided sample products for evaluations.? You can see some of those reviews by visiting our site here.? As Thecus is a major product provider in this category, we want to offer you the opportunity to have your products included in our series.

We encourage equipment manufacturers and software developers to check out our reviews.?We promise to be thorough and fair in all of our reviews.? We hope you will take part in this comprehensive review of NAS products and are attaching our Product Submission Guidelines to assist you.

Should you have any questions or wish more information, please feel free to contact me.

Best Regards,

David

Hi:

Thanks for your note. Yes, it appears my issue has been resolved. In looking at some of the html I discovered that some extra code was being placed on the page which appears to have been due to some formatting I added when creating the source document in Microsoft Word.

Now that I am aware of what is happening I am able to prevent it by not putting formatting in the document or saving it as plain text.

Regards,

David

Bill:

Just to close the loop on this (in case you are interested), it turned out that there was a major flaw in the theme that I use and as a result, the entire bbPress forum was incorrectly set up. I had built in an extra layer in the forum structure in order to see the forums and that extra layer caused the Oh Bother box to appear, along with a host of other issues.

A person on the bbPress support site wrote a bbpress.php file that corrected the error in the theme. I had to restructure the forum hierarcy but that corrected the underlying problems and with it the Oh Bother! error messages.

The css you provided to correct the text color is still working so thank you for that.

The new php file has revealed an error in another plug in that I use to put a log in/register link at the top and the bottom of the forums but I have posted a note on the plug-in authors site to ask for assistance with that.

All in all, between your help and the other help I received, I have come a long way. If you take a look at the site now, I think you will see it looks a lot better.

Thanks again.

David

Bill:

By the way, I did post this on the bbPress forum but no one has come up with an answer or even a suggestion at this point.

Regards,

David

Bill:

This code didn’t seem to work but I appreciate you trying.

I have certainly taken enough of your time. Thanks for all of your help on these issues.

Best regards,

David

Bill:

I’m wondering if I can impose upon you with help on another problem. I’ve already posted this earlier today but no one has responded yet.

On the Forums page, towards the bottom is a default box that says:

“Oh Bother! No topics were found here.”

It appears because it is an index page of topics and forums so there won’t ever be topics there. There is also a box underneath that box that says:

CREATE NEW TOPIC IN”APPLE TECH TALK FORUM”

I installed Firebug and located the code for both (they are very near each other) and this is what I came up with.

<div class=”bbp-template-notice”>
<p>Oh bother! No topics were found here!</p>
</div>

<legend> Create New Topic in “Apple Tech Talk Forums” </legend>

The second entry is part of a bigger div statement that defines the larger text box.

From the little I have learned I think these are HTML statements and not CSS statements so putting them in Custom CSS won’t help me.

Is there an easy way to get rid of both of these lines?

I have left the forums unlocked in case you need to get into them.

Thanks,

David

Bill:

I will check it out.

Thanks for all of your help. I really appreciate it.

If you are done, I will mark this issue as resolved and lock down the Forums again.

Regards,

David

Sorry, I opened it up again for you.

I do use Firefox. Do you suggest I add the Firebug plug-in? Does that make things a bit easier?

Bill:

Yes, that seems to have do exactly what I was looking for. Thank you so much.

Can you point me to what you looked for in the browser inspector to figure this out. I looked for the code but got completely lost.

Thanks again for your help.

Regards,

David

Bill:

That is the section I am referring to. I have temporarily removed the registration restriction to give you an opportunity to look at this further.

I tried using the browser tools earlier but I’m afraid I don’t know enough to know what I am actually looking for and then what css to create to fix it.

So, I would appreciate your additional assistance with this.

I am brand new to WordPress and while I have learned a lot in a short period of time, it seems like for every new thing I learn I discover two more that I need to learn.

Thanks again for your help.

Regards,

David

Bill:

Thank you! That is exactly what I was looking for. The text in the blog comment box is now black. Unfortunately, it did not carry over to the bbPress post/comment box. Any idea what the code would be for that?

Thanks,

David

I think I have resolved this and want to share what I did in case it can help others.

Switching themes did not resolve the issue which indicated to me that the offending text was not associated with the theme’s function.php file.

As is often suggested for many issues, I deactivated all of the plug-ins and saw that the offending text went away. I then re-activated the plug-ins one by one and eventually found that the Subscribe2 plug-in was generating the offensive text (even though I still can’t find where I might have added it in). A reset of the plug-in using the provided reset function seems to have cleared the problem.

Thanks to everyone who offered assistance in this issue.

regards,

David