dalkinn

Indeed, thanks for the followup and solution had I proceeded along the way I did, dumbusername.

With that, I now understand why it is set up the way it was, though I certainly wouldn’t have guessed as such. On my server, I just run the one website/blog so the yum installation method just ended up complicating things. Next time I’ll just download and unzip!

The yum install of wordpress. It’s included on the Fedora Discs… certainly 9, but I think it was on 8 as well.

That said, if there is one, the responsibility for any package differences or install differences rests on the person or people that are maintaining the repo, not anyone here.

My comment was not really directed toward you or anyone in particular, but intended more as a caution for others that decide to install WordPress that way. There is also the small chance that the individuals responsible for that package might be around and read these forums.

Okay, while I think everyone’s given up on this, I did find a solution, though I’m not certain of the cause. I reinstalled with yum (doing a remove, deleting all my web files, then reinstall) and reset the databases just to find the same issue.

After that, I deleted the web files again and downloaded the zip and installed that way. The themes showed up. As far as I know, the only difference between the two methods is that yum will locate the files in /usr/share which need to be copied, but the more notable difference is that the wp-config.php file is located in /etc/wordpress instead of the root web directory.

After the themes were working, I decided to set up the symbolic link to the /etc/wordpress location again, but after doing so I lost all the additional themes in the panel. After I realized that broke theme selection, I returned it to its original condition. This still didn’t fix it, so I just reinstalled the downloaded file one last time and I’ll leave it as such.

It leads me to suspect there’s something with the symbolic link to the config file that is causing the issue, but it could be something with linux permissions, pathing, or even a bug. Removing the symbolic link should have fixed any of those issue if that were the case, so it could easily be something else causing the issue.

I’m going to go ahead and tag this thread as resolved, but I do think that someone should look further into the difference between the yum installed and downloaded versions. I could find very little information on this site regarding yum installation, so perhaps it’s unusual or atypical that WordPress would be installed that way. However, since it is possible, it would probably be worth mentioning, even if this is the only difference between the two.

Shameless bump ??

I don’t think it matters, but I installed wordpress via yum, rather than the download. I might try deleting and installing via the download, but I don’t see why it would matter.

Anyone else have an idea? I see in the last few days there have been a few similar threads, but they were all unzipping/directory issues, not similar to mine.

Anyone have any other ideas to try? For kicks I tried giving the themes full permissions (777) but that didn’t do anything different. The two that wordpress comes with have limited permissions anyway, but I thought it was worth a try.

That nutone theme is one of the ones that doesn’t work…

I’m glad you told me it’s good error reporting is off, since I wouldn’t have known otherwise, heh.

https://www.davisondesigns.net

Could there be something with permissions/ownership of the files? Does it matter who owns them?

I downloaded two more themes from a different site. Still no new themes appear on the admin panel.

Do you have a way to check the contents are correct? I have a hard time believing that five different themes have incorrect contents. This is making me crazy.

I should add that the new themes aren’t double-directory listed. The style.css file is in /wp-content/themes/<theme>/