sweetangst

bump

@sweetangst: Don’t you think that’s just a little condescending?

Yes, I do. But I’ve also seen plenty of people get answers that were WAYYYYYYYY above their heads because they asked a simple question and the person reading their question assumed the OP was already familiar with the basics of WordPress use… when in reality, he/she wasn’t and only required a simple answer.

Why do you think real tech support workers always ask you “Is your computer plugged in? Is it turned turned on?” before they actually address your question? You are assumed to be an newbie until proven otherwise because if not, the tech support person might go into some long withdrawn jargon that only techies understand and the person asking the question just gives up because they think the subject matter is way beyond them.

“Angst” is part of the username for a reason.

That should not affect the visibility of your comments to the public.

To test, simply log out of your blog and revisit your page.

To limit the amount of posts on your main post page, go to:

Dashboard -> Settings -> Reading Settings -> “Blog pages show at most”

And change the number to a more reasonable one for your needs.

Add her as an author to your blog so that she has her own username/password etc and then get a plugin that adds your signature to the bottom of your posts, like this one:

https://www.dagondesign.com/articles/add-signature-plugin-for-wordpress/

*I haven’t used that plugin, it’s just an example. I’m sure there are other ones out there.

https://mu.www.ads-software.com/

Try going to your file manager via your host’s website. There will probably be a way to select the directories you want via their web interface and change the permissions.

Reverse engineer the Arras theme.

If you don’t know how to do that or at least start that process, we can’t just give you a simple answer that you’ll understand.

Seriously? You’re going to confuse the original poster. Keep it simple.

You all give the people asking the questions entirely too much credit. They have a simple problem and want a simple solution. Stop trying to overcomplicate it just because you can.

This should also work to fix all your image links and etc since you do have backups of the SQL file..

https://wpbloghost.com/wpbloghost-home-school-for-wordpress/how-to-move-your-wordpress-blog-from-a-subdirectroy-to-root/

Watch this video:

https://wpbloghost.com/wpbloghost-home-school-for-wordpress/how-to-move-your-wordpress-blog-from-a-subdirectroy-to-root/

If you want to try the “fixing the links in the database method”, then read this entire article and make sure you only use what applies to you.

https://wptoy.com/tips-tricks/fix-missing-images-during-wordpress-database-import/

I have a database plugin that emIls me backups of the SQL every weekend.

Yeah, that would have been nice to know from the beginning…

could someone give me a simple solution to changed the paths on all my images?

The simplest solution would have been to just create a fresh wordpress install at the root, export the posts/comments from the old one using the built-in WordPress tool, and then import it to the new one and check the little “Import file and image attachments” checkbox and hit “go”…. but… since you’ve already moved everything to the root, you only have a few choices and all of them stink:

1) Follow one of the “convluted descriptions” to change the image paths in your database… which generally just requires an sql statement to physically change the new database (ALWAYS HAVE A BACKUP FIRST!)

2) Export an XML from the old blog using the built-in WP tool. Open the new database with phpmyadmin & empty (NOT drop) the tables that the XML file needs to replace, and then import the XML using the WP import tool.

3) Start over and play the fresh install / export / import game – but note that this won’t copy any of your custom database tables that your plugins or theme may have created.

If anyone else wants to add an easier way, feel free to step in and correct me…

Where’s the trust?

I inspected your page elements with Google chrome. Your main-blog div is NOT closed prior to your sidebar div.

Just because it has a little HTML comment next to a </div> tag doesn’t mean it’s actually closed hon. That </div> could just as easily belong to another div nested within your main-blog div. The only way to know for sure is to look at the code and make sure all the <div> tags have </div> mates and make sure that main-blog is closed prior to sidebar.

Were you looking in the right template page… I’m guessing it’s probably either in single.php or archive.php. It’s obviously not a problem on the index.php because that page works.

FYI – Your footer needs some love (e.g. your css isn’t enclosed in <style> tags, there’s other random stuff, and it isn’t aligning properly on some of your pages) and your google ads are jacking up your whole theme, look at your About & Contact pages.

Since the lightbox is working, you’re doing everything right as far as adding it to the page goes.

None of the modifications that you do to the photo in the Add Media window will affect the lightbox CSS behavior.

There is probably some conflict between your CSS & the lightbox’s CSS.

To test that, you could simply rename your theme’s css to style_temp.css or something and then try the lightbox again to see if it’s built-in CSS will behave properly. If it does, then you have something in your theme CSS that is conflicting with it and making it act weird.