If you were talking to me, I do not believe I have access to my Apache error logs and even if I did, I'm not quite sure I'd know where to find them. I will email my host's support and see. As you can tell, I don't exactly know much about php or hosting, I needed a lot of space to host some pictures for an unrelated thing, so I figured the best thing to do would be to buy a domain with a decent amount of space and bandwith. Then, I figured, why let a domain name go to waste, and started building a website about a week ago. I chose php because a few of my favorite sites were using it and I chose nuke because it seemed easy enough to handle and the community seemed great - certainly reaffirmed today. Anyway, I am rambling on, as soon as I finish my site, I'll be sure to announce it here. It's a site for a playing card game I invented. It's sort of a variation on war and poker and well, you'll see. Thanks again for the help.
Stezez Nuke Soldier
Joined: Jul 23, 2003
Posts: 11
Posted:
Mon Jul 28, 2003 1:55 pm
I suppose I should post a reply rather than editing my posts, it seems to cause less confusion. I use bulletproof ftp or my hosts's ftp website interface. In terms of binary, I use whatever the default is.
Raven General
Joined: Mar 22, 2003
Posts: 5233
Location: USA
Posted:
Mon Jul 28, 2003 1:57 pm
Just for curiosity, did you use the same ftp client both times with Site Info?
I used bulletproof the first time and since I was at the website interface checking what blocks I had in my directory, I used that the second time. Hmm....
Raven General
Joined: Mar 22, 2003
Posts: 5233
Location: USA
Posted:
Mon Jul 28, 2003 2:02 pm
I would next, if you care to try to find the difference, see what the default ftp mode is for each (binary or ascii) with *.php files.
I am pretty sure they are both actually binary as in bulletproof there is an option to make certain extensions ascii and php is not set as that. In terms of the hosting site's file manager I do not know, but I would assume it has binary as default and if this is a common thing with php, they probably would have it set correctly as they have a lot of support for php on their site and seem to know what they are doing.
Audioslaved Elite Nuker
Joined: Jun 14, 2003
Posts: 420
Location: Hawaii and The Fan Forum
Posted:
Mon Jul 28, 2003 2:44 pm
OKay, this keeps getting weirder for me,
Thankfully enough, my mozilla browser was never logged out as admin(cant login as admin on IE). I am trying to add a block and it is doing the same thing, when I press submit, it does not take me to Block Admin it takes me to index.php, and the block was not added. Everything seems to be refreshing at index.php. Since I can no longer add blocks, or login for that matter. I am going to just replace all files from my last backup and upload my db from last backup, hopefully this will resolve the issue altogether and I will never touch this again. LOL!!! I will let everyone know how it goes, I have to say, that I have never experienced anything like this before, and if I find out how to replicate the problem, I will post here so we can come up with some sort of solution for it.
Stezez Nuke Soldier
Joined: Jul 23, 2003
Posts: 11
Posted:
Mon Jul 28, 2003 2:54 pm
I am pretty sure that my problem was not the same as yours Audioslaved, so this may no longer be of help to anyone; but, I actually figured it out! I compared my script uploaded with bulletproof to the one I have up now and somehow the second to last line: $content .= "</form>"; got deleted. I tried removing it on my working block-site_info.php and I get the old problem, the site info block works fine except for logging in. So, can someone explain to me how that works, why was the logging in not working because of a missing: $content .= "</form>"; and why did everything else still work? Thanks for the input.
Audioslaved Elite Nuker
Joined: Jun 14, 2003
Posts: 420
Location: Hawaii and The Fan Forum
Posted:
Mon Jul 28, 2003 3:48 pm
The problem exists in the block table in the database, I am not sure why this is. Here is my troubleshooting to prove that.
I re-uploaded my files and db to the site and attempted to login, it worked successully. I went to admin and cleaned up my blocks, deleted all inactive blocks that are no longer needed, and moved a block on my main page from the right side to the left side. Upon doing this, I logged out to see if everything was good, when trying to login, the same problems started occuring again. Considering the only change I made was to my blocks, I uploaded my blocks table, refreshed the site, and attempted to login again, It worked, I am able to login, What the heck does removing and moving blocks have to do with logging in, I dont see how this could throw that off, but I will look into it further, can someone else try moving one of there blocks from right to left and deleting and inactive one and tell me what you get. Thx.
Raven General
Joined: Mar 22, 2003
Posts: 5233
Location: USA
Posted:
Mon Jul 28, 2003 3:52 pm
Stezez wrote:
I am pretty sure that my problem was not the same as yours Audioslaved, so this may no longer be of help to anyone; but, I actually figured it out! I compared my script uploaded with bulletproof to the one I have up now and somehow the second to last line: $content .= "</form>"; got deleted. I tried removing it on my working block-site_info.php and I get the old problem, the site info block works fine except for logging in. So, can someone explain to me how that works, why was the logging in not working because of a missing: $content .= "</form>"; and why did everything else still work? Thanks for the input.
Logically the script would have continued loading until it found an end form tag. Then depending on what was in that remaining htmle, anything might have happened. All code above it was safe. The bigger question to me is how a whole line would get dropped? We may never know.
The problem exists in the block table in the database, I am not sure why this is. Here is my troubleshooting to prove that.
I re-uploaded my files and db to the site and attempted to login, it worked successully. I went to admin and cleaned up my blocks, deleted all inactive blocks that are no longer needed, and moved a block on my main page from the right side to the left side. Upon doing this, I logged out to see if everything was good, when trying to login, the same problems started occuring again. Considering the only change I made was to my blocks, I uploaded my blocks table, refreshed the site, and attempted to login again, It worked, I am able to login, What the heck does removing and moving blocks have to do with logging in, I dont see how this could throw that off, but I will look into it further, can someone else try moving one of there blocks from right to left and deleting and inactive one and tell me what you get. Thx.
I did what I think you described and it seems ok here.
I compared the nuke shipped sql file with my table, everything seems in order there.
I will check this out some more. I am going to get it down to which block it is causing this problem, (more than likely a custom block on my site) I will put up here what code is causing the problem when I figure it out. I think I may already know the culprit. I'll let you know. Thx for checking it out Raven, it has to be a custom scrolling block I made for my Nuke 6.0 site that I am using on my 6.5 site as well. Some code in it has to be messing everything up.
OK, i found the culprit, it is my quiecomm shoutblock, I deactivated all blocks except for my main menu and user menu and started activating them one at a time, each time logging out and logging in, when I activated the quiecomm block, logged out and tried loggin in, it would not allow me to. There has got to be some code in this that is causing this to happen. For some reason when quiecomm and the language block are active on my left side the problem does not occur, if I deactivate my language block, then quiecomm prevents me from logging in, there has to be some coding issues with that block. Any ideas.
I downloaded the modded Quiecomm Shoutblock from http://www.ourscripts.net and uploaded it, there are no problems now. Not sure why that was happening, but at least its all figured out now. I looked through the code and tried to find what it was but can't really see it, I will have to compare the two files and see what I can come up with. Problem fixed.
Quiecomm shoutblock v2.4 had a lot of issues with the interface when i first downloaded it. I have since fixed a lot of the problems and have even enhanced it some too. The problem with the login on the other block sounds all too familiar also. When php nuke v6.5 first came out, that block couldnt log anyone in. I quickly fixed it and enhanced it quite a bit.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
