Member stats
|
| |||
| 08:41am 30th Jan 2010 |
|
Quote:
I just tested the admin panel in FF 3.6, IE8, Chrome 4. The menu links all work as they should do. Can you tell me which versions of each browser you're using so I can try replicate the problem? firefox 3.5.7, chrome 3.0.195.38, internet explorer 8. i'm not convinced it's a problem with the browser though, as it works perfectly on my windows pc running apache and php but not on the webhost. the webhost is also windows, running apache but i'm suspecting they have something disabled that is required... ...towards the end of the installation on the webhost, there is a very very brief flash of what looks like an error message relating to either fclose() or fopen() which is only displayed for a fraction of a second - i tried emptying the database and reinstalling while running video capture software to capture the exact frame but can't replicate the error, although the symptoms are the same. is there a reason why fopen() and fclose() would be disabled on the server-side and would that in turn affect the javascript calls to display the admin menu? how would i test this? thanks for your time chris. | |||
| 07:21pm 30th Jan 2010 |
|
There is no reason that any PHP server side settings could affect the client side Javascript code. The only thing I can think of is if the server is altering the document, possibly adding something to it before it outputs it to the browser. Just had a thought at what might be causing this to happen. When you're logged into the admin panel, can you view the source of that page and look for any php errors, was thinking that if there was an error in the php code where the menu is you may not see those errors as they might be hidden in a menu that has yet to be expanded. | |||
| 07:27pm 30th Jan 2010 | Last edited by Chris at 07:55pm 30th Jan 2010 |
|
Quote:
The installer uses fopen and fwrite to write the database connection settings to the db.php file, it might be throwing an error because it's unable to write to it. Did you try CHMODing that file to to 777? If you managed to login previously it would suggest that it wrote the information to the file anyway so that shouldn't matter. to all intents and purposes, it seems all is well - the tables etc are created and populated and it's all green lights on the admin panel side. i did the equivalent of CHMOD in the webhosts file manager on db.php - i even tried giving write access to every file and folder down the tree but still nothing. Quote:
Just had a thought at what might be causing this to happen. When you're logged into the admin panel, can you view the source of that page and look for any php errors, was thinking that if there was an error in the php code where the menu is you may not see those errors as they might be hidden in a menu that has yet to be expanded. this gets weirder (well to me anyways, not being php programmer). on looking at the source code near to the none functioning options button i spied the links for what would be under the options section when clicked. if i append any one of them to the admin.php url it will open the requested page fine, with the full section expanded in the menu - news, options etc. upon clicking the same header in the menu it doesn't collapse and likewise other menus still do not expand upong clicking. HOWEVER the first time i appended one of the actions to admin.php (the 'accounts' page i believe it was) i got the following message, which i can't replicate: Warning: mysqli_connect() [function.mysqli-connect]: (HY000/2003): Can't connect to MySQL server on 'mysql8.brinkster.com' (10060) in C:\Sites\Single39\SITENAME\webroot\music\mysqliclass.php on line 56 Warning: mysqli_select_db() expects parameter 1 to be mysqli, boolean given in C:\Sites\Single39\SITENAME\webroot\music\mysqliclass.php on line 57 Warning: mysqli_prepare() expects parameter 1 to be mysqli, boolean given in C:\Sites\Single39\SITENAME\webroot\music\mysqliclass.php on line 104 Unable to prepare: SELECT registrationaccess,registrationallow,commentslength,furlextension,furlenabled, furlprefix,furldirname,spamtime,spammsg,commentmsg,commentapprovemsg,timezone, bannedmsg,catdelimiter,useimgverification,salt,version,scriptpath,sendtodelay, regcomment,commentsnotify,registernotify,emailnotify,unapprovednotify,filetime FROM news30_options WHERE 1 Arguments: | |||
| 08:15pm 30th Jan 2010 | Last edited by Suishide at 08:26pm 30th Jan 2010 |
|
If you edit the mysqliclass.php file, around line 56~ you'll see this Code:
$connection = mysqli_connect($cfg['hostname'],$cfg['user'],$cfg['pass']);
change that to Code:
while(!$connection){Save then see if it still gives the error message where the menu items are. | |||
| 08:26pm 30th Jan 2010 |
|
i've turned on error reporting in internet explorer, whenever i click a javascript menu item i'm getting an error like this: Message: Syntax error Line: 1 Char: 1 Code: 0 URI: http://www.SITENAME.co.uk/music/js/main.php Message: Object expected Line: 1 Char: 1 Code: 0 URI: http://www.SITENAME.co.uk/music/admin.php? always one syntax error for main.php, followed by differing numbers of object expected messages for admin.php. at a push i'd happily settle for just having all menus displayed/expanded permanently using php/html if there's an easy way to do that? | |||
| 08:47pm 30th Jan 2010 |
|
Editing files to have all the menu links shown constantly isn't really addressing the problem instead just masking it. The problem may occur on other sections of the script unless the MySQL error has been fixed. | |||
| 08:50pm 30th Jan 2010 | Last edited by Chris at 08:53pm 30th Jan 2010 |
|
since the actual links to all the menu options are present in the source code of the displayed pages, if i wanted to replace where the links are generated to bypass the javascript dropdowns and display them directly, which file should i be looking at? | |||
| 08:59pm 30th Jan 2010 |
|
Code:
if(DataAccess::getaccess("news")){
which is basically checking to see if the user has access to the news section (via access levels), if they have access then it'll show that menu, so instead you could change that to something that will always be true, something like Code:
$i = 1;This way it'll show the menu regardless of if you have access to it or not. You'd need to do this for every instance of DataAccess::getaccess in that file so it may take a bit of time. | |||
| 09:05pm 30th Jan 2010 |





