owlsheadbiz

Drat – my spaces didn’t show up. Once more with feeling:

Now you see:
public_html

• wp-admin
• wp-content
• wp-includes
• wordpress

Once done you will see:

public_html

• wordpress

• wp-admin
• wp-content
• wp-includes

Well, the new directory should be at the same level as the wp files, but I caution you to review the Giving_WordPress_Its_Own_Directory link before dragging them over.

There is a place in the WordPress admin interface (dashboard) where you indicate where the wordpress files are stored. It’s been a while since I’ve done this (and I refer to the documentation every time, to be safe) – I believe there is an order to the proceedings that must be followed to avoid heartache and strife. ??

I don’t recall if you change the setting in the admin panel first or move the files first… or if you even need to move the files once you’ve changed the setting in the admin panel. Sorry – I’m just heading to bed and don’t have it in me to review the documentation at the moment.

Now, when you view your files through DreamWeaver, you see:

public_html
wp-admin
wp-content
wp-includes
wordpress

Once you have completed the process, in your directory list you will see:

public_html
wordpress
wp-admin
wp-content
wp-includes

The first three folders will be moved into the wordpress directory. The “loose” wordpress files should also go into the wordpress directory.

Right, I’m done for the night. Good luck!

Also, I should note – the web server in question runs php 5.2.17. Not sure I have much control over that, and the client is in the midst of a big fundraising push. I don’t anticipate moving the site, at least until the campaign is completed next month.

Oh good! I agree – when I started out, the most basic of WordPress documentation gave me pause. It does get better as you become more familiar with the lingo. Best of luck!

Well, no harm done, really … but DreamWeaver will be of little use outside the ability to upload and download your site files. I mean, if you really want to get into editing the php files, but it sounds like you’re not quite there yet. ??

So, when you look at your local and remote files in DreamWeaver, the suggestion is that you move all the wp-specific folders and files into a subfolder called, blog (actually, I would suggest ‘wordpress’). By subfolder, we mean a folder “under” (sub) your domain. So, when you connect via DreamWeaver, you would add a new folder to your site.

Then, when you go to view your new WP site as you build it, you will go to https://yourdomain.com/wordpress. Technically, this page is visible to the world, but you can attempt to block anyone from finding it using a robots.txt file.

Now – the folks above posted a couple resources about moving your WordPress files around, which I suggest you read. It is possible to move all your WP files into a subfolder (called wordpress), then when you are done creating your masterpiece, you can set WordPress to show the main page at your domain root while holding all the WP files in your subfolder. In other words, you wouldn’t have to move all of your files again.

You would have to do away with your current home page. I suggest creating a folder called “previoussite” when you’re ready to make the switch and moving all of your current site’s files into it. That way your root directory will be nice and clean – and you can get that old site back pretty quickly if you run into any trouble when you launch your new WordPress site.

Hope that helps and doesn’t further confuse!
~KJ

I’m afraid you have entered a whole new world. WordPress should not be edited via DreamWeaver… it sounds to me as if you are using the ftp function of DreamWeaver to view the files on your server, is that correct?

Oh boy, I was completely unable to log into support this weekend – don’t know what was going on. Anyway, sorry for the delay.

1. Enabling accessibility mode did not work.
2. My client is happy to leave the widget as it is, so I am not going to play with it anymore. I hope any new widgets we add don’t replicate this problem! So far, other widgets have sometimes been very slow to save, but they have all worked.
3. I don’t have aching enabled on the site (that I know of). I will try another browser – maybe Firefox is acting up. I have not tried all the plugins, if it comes to that I will do so.

Thanks again for all your help. I’ll report back here if I run into additional problems. For now, I’ll mark this resolved since she wants to leave it as is.

~KJ

Thanks very much for your responses – I will check out these options and report back tomorrow. ~KJ

I should clarify – when I open this text widget in the admin panel, I can make changes to my heart’s content. But when I click on Save or Delete, the little wheel spins endlessly. I’ve left it for hours before. So I want to know if there is a backend way to delete a text widget – through the db, perhaps? without using the admin panel.

I missed something you said earlier – I checked the sidebar php file previously, and this widget is not hardcoded.

Thank you for your help – I appreciate it.

Oh, I’m not trying to change the color from within styles.css – I’m trying to remove one of the color codes from within the admin panel. I have access to the widget through admin, and can make changes to all of the other widgets, but this one text widget won’t let me edit or delete it. At this point, I’d be happy to delete it and start over with a fresh text widget, but it times out when I try to do anything, including deleting it.

When I say make the entire box clickable, I meant all of the content within the box. Although… it might make sense to hard code it in the sidebar php file. She would be happy with the entire thing truly being clickable, rather than just the content. On the other hand, I don’t believe she would be comfortable editing the sidebar php file… even the widget admin panel frustrates here from time to time.

Either way, I can’t remove that widget through the admin panel and I’m at a loss as to how to get rid of it.

Here’s the entire code as it appears in the widget admin:

Title field: /empty/

Text field:

<h3 style="margin-top:0; color:#115D2F !important;"><a href="https://www.fairycongress.com/" style="color:#FFFFFF !important;">Fairy and Human Relations Congress</a></h3>

I've been invited to present three workshops at the Human and Fairy Relations Congress, June 28–July 1, in Washington State. I'd love to see you there!

<a href="https://www.fairycongress.com">

<img src="https://i589.photobucket.com/albums/ss336/yarrowphoto/spiraldance1_zpsf6530b28.jpeg"></a>

I hope that comes through clearly, I’ve never pasted code in here.

I am hoping to clean up the color codes on the h3 link and make the entire paragraph into a link (she wants the entire box to be clickable).

It’s the Fairy and Human Relations Congress widget.

Thanks. I considered using display: none, but I would like to solve the problem as my client is likely to add more text widgets in the future.

The site is: https://thrivingplanet.org/counseling/

No one is seeing this problem? I can’t imagine I have two clients and they are the only ones?

Hi, I posted a question here, but figured it out on my own. Nevermind. ??