The Package must be broken
-
I really must say that I am disappointed with all of the “hype” around WordPress. The only times I ever had this much trouble getting a CMS to work were 1) the first one I ever installed and set up (and I have done many), and 2) CMS’s that were so hopelessly buggy that I simply flushed them from the server and used one that actually worked.
That last phrase, that actually worked, is extremely important. I realise that not everything works correctly “as is” on every server. But every CMS I have ever successfully used had documentation with it that covered every aspect of the install in step by step instructions.
More to the point, I have never successfully used a CMS that didn’t have information in the <b>”Read Me” or “Install Readme”</b> file regarding the proper [em]permissions[/em] settings for every file in the CMS system.
For example:
1) Upon install I was not allowed to edit and update the Welcome! message. This was a permission problem that I think (I hope) I have resolved. I finally got the post to update, though I never changed any file permissions. Honestly, I do not know how I got it to update other than waiting 24 hours and trying again. And even then, it took several presses of the “Update” button on the admin post editor page.
2) After unsuccessfully trying two alternate theme installs, I switched back to the default theme, twentyten, and tried to upload a new header image. It simply would not allow me to do so. I used chmod multiple times to allow write access and each time I changed it and retried the upload the settings somehow switched back to deny access. Again, after many repeats of this process it finally allowed me to upload the image.
3) I tried to edit the “About” page. The admin panel shows the page to exist. But when I click on the “About” page link on the site main page, it leads to a “404:file not found”. On the admin page, my edits are saved as drafts and show in the page directory. But not even the sample “About” page is available from the site home page.I have unsuccessfully found nothing that clearly describes what files on the server need to be set with what file permissions. Perhaps I am simply not finding the information. But it would seem to me that such a vital piece of information would be more prominent in the documentation somewhere. It has been with every other CMS I have ever used.
Out of desperation I chmod the entire wp-content folder 777 and recursed into subdirectories and it would still show 404:not found when I click on the “About” page link. So, just for giggles, I have chmod the whole of every file in the WP platform to 777 (absolutely not a good idea for standard operation IMHO) just to see if it would allow me to add the “About” page. And guess what: it didn’t. This platform will not allow me to add images, posts, or pages, which leads me to the only possible conclusion: the package is somehow broken. And I have wasted three days of my life that I will never get back on it.
Please forgive my frustration. WordPress is an attractive CMS. And apparently thousands, if not millions, of people use it all over the world. But I would REALLY appreciate knowing where the secret key to making the platform actually work from the admin panel is. If it doesn’t start working right pretty soon I will reluctantly flush it and start over with a CMS that works. I positively HATE using forums! I hate having to open an account somewhere by giving my email address for something that I have no intention of using more than once or twice. If it takes more than a couple of questions to get running, it is absolutely not worth using.
- The topic ‘The Package must be broken’ is closed to new replies.