Posts: 14
Joined: Feb 2011
Reputation:
0
mwkurt/prophetizer
I have the same problem. I fixed part of the PEAR problem. Go into your php directory and run 'pear-update.bat'
If you are receiving the 220 error, make sure you check the curl in php.ini, save, stop apache and mysql and then restart both.
After that, both should work.
Posts: 14
Joined: Feb 2011
Reputation:
0
If I were to guess, the one computer that is working is running off of cache file. I'm far from being an expert, but I would start the process of rebuilding the webpage.
1. Make a copy of your current setup, htdoc or what not.
2. Copy a brand spankin new web directory.
3. Verify everything works. (I can help a little more if you let me know what server/program you are using)
4. Edit the config and layout
5. Verify it works
When updating the config files, do one section at a time. Yes, you will have errors in the widgets that are not correct. But it will help you localize where the errors are coming from. Thats how I figured out the PEAR/CURL errors. Most likely, your layout/css files became corrupt.
Once you get a working base model, make a copy of that entire web directory. It will make it easier to restore if you find the bug causing the problems.
Posts: 283
Joined: Sep 2008
Reputation:
2
i updated pear from the website, no issues there now, but i can't use IE or chrome to get menu links, i use chrome as my default browser so this would be nice. i am using the chrome dev channel version, don't know if that is why or not.
--
Posts: 1,328
Joined: Mar 2010
Reputation:
19
mwkurt
Posting Freak
Posts: 1,328
How did you go about updating once you got there? When I tried, it made no difference to my errors.
Mark
Posts: 283
Joined: Sep 2008
Reputation:
2
looks like i lied, i ran the update and it didn't fix my deprecated errors, so i renamed the PEAR directory, that fixed it. i don't like that solution, but i haven't found any others yet
--
Posts: 14
Joined: Feb 2011
Reputation:
0
Prophetizer - Steve is having the same problems as you. I typically use Firefox, but will try IE when I get home. It is possible that the browser is not able to display the php stuff.
Mwkurt - Once you run the file, a DOS window will pop up. Let it run, it will take a bit. It will close once it is complete. After that, restart your webserver and clear the cache out of your browsers.
Posts: 2,838
Joined: Dec 2006
Reputation:
2
I uninstalled and installed everything again. Now, I am getting the same error as you guys do plus my menu bar is not working in Chrome.
Not sure whether I understood your solution, can you elaborating what your renamed and/or updated?
Server: Asus Sabertooth Z77 | Intel Core i5 3.4 GHz | 16 GB DDR3 | 128 GB SSD, 82 TB (9 x 6 TB, 7 x 4 TB)
HTPC 1: Raspberry Pi 2 | HTPC 2: Raspberry Pi 2 | HTPC 3: Raspberry Pi
Posts: 283
Joined: Sep 2008
Reputation:
2
i just renamed the PEAR folder, since it isn't needed. but i'm going to try the update as ncfitzge suggested.
and, IE and Chrome can display PHP just fine so i'm not sure what you meant by that ncfitzge.
--
Posts: 283
Joined: Sep 2008
Reputation:
2
well i figured it was a CSS issue, and i was right. this CSS is made specifically for Firefox/Mozilla browsers i imagine.
so in the nav.css file, under #nav-menu, comment out width: 2000px;
i don't know why this is like that, it doesn't even make sense to me. but this explains the various issues with other browsers. it's almost useless in IE, but thats fine for me lol, maybe i'll take a look at the css and make it work a bit better all around.
--