1
toonstruck
Re: Xoops Files Corrupting when Uploading via FTP
  • 2005/8/26 19:19

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


No.. im using ascii..

It literally is leaving only a line or two of the old php code in there. And that does not happen all the time. very odd.



2
toonstruck
Xoops Files Corrupting when Uploading via FTP
  • 2005/8/26 17:37

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


I mentioned this problem when upgrading to 2.2. Now I realize the problem wasnt just a one time occurence. When upgrading to 2.2.3, Im getting the same thing.

When I try to upload php files that already exist on the webserver (trying to overwrite new xoop patch over existing installation), it sometimes mixes the old and new PHP files together- therefore corrupting them.

I've tried three different FTP programs now. Have you ever heard of a problem like this? I can't figure out what is going on. The funniest thing is, this is only happening with XOOPS patches. I've never experienced this with the forum software I'm running or various other PHP packages.



3
toonstruck
Re: Strange PHP code printing on my Xoops pages
  • 2005/8/25 16:24

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


Thanks guys!!!


Bryo and Frankblack, you were right. Both the footer and header files were screwed up. Evidentially the index.php file was messed up too. It seems that the files somehow mixed old code and new code together. That leads me to believe there are plenty of other files that are corrupted too. I have no idea what could of gone wrong.

This weekend I will back up the directories, then delete all the files and re-upload them as suggested.



However, for now I am no longer getting the strange code.


Thanks again! Much appreciated. :)


Now if only I could get the admin section to work properly. :(



4
toonstruck
Re: Strange PHP code printing on my Xoops pages
  • 2005/8/24 15:53

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


Since it doesnt seem that anyone knows what is causing this problem.

What happens if I delete all the files and complete re-upload all 2.2.2 files? Will that cause any problems? I'm hoping that that will catch any screw ups that might of happened along the way.

I've had about all I can handle with the problems that this upgrade has made. I'd hate to abandon XOOPS completely. I'd like to try something else before giving up. And if this can be tried without making things worse. I'd like to do it.



5
toonstruck
Re: Strange PHP code printing on my Xoops pages
  • 2005/8/21 7:41

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


I turned on Smarty Templates debugging. I noticed that

$xoops_contents says:

"oopsTheme['thename'] = $GLOBALS['xoop..."




This is the start of the same text that is printing on that particular page. I dont know if this means anything to anyone. But perhaps it can help narrow the problem down.


Thanks.



6
toonstruck
Re: Strange PHP code printing on my Xoops pages
  • 2005/8/21 7:19

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


Thanks for the reply. No, GZIP compression is off on Xoops.


This is a bummer.. Any other ideas?



7
toonstruck
Strange PHP code printing on my Xoops pages
  • 2005/8/20 4:57

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


Im running version 2.22. If I go to any page of my XOOPS installation, the following text:

"oopsTheme['thename'] = $GLOBALS['xoopsConfig']['theme_set']; } $GLOBALS['xoopsLogger']->context = "module"; ?> ?>"



And at the very bottom of the page:

"& $xoopsUser && $xoopsUser->isAdmin($xoopsModule->getVar('mid'))) { echo $xoopsLogger->getSQLDebug(); } } ?> ?>der.php"; require "footer.php"; } ?>"



Does anyone know what is causing this and how I can fix it? I have no clue on where to look. :(

It makes no difference what theme I am running.


Thanks



8
toonstruck
Re: Upgrade from 2.013 - 2.2 -- admin.php is blank
  • 2005/8/20 1:29

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


After doing some looking at other peoples posts in this forum, I see that others are having the same problems.

I was able to get in various parts of the admin section by going directly to the URL with "fct" defined in the URL.

However, this is pretty clumsy and I did not see any fixes for this situation. Did I miss a fix somewhere? Can someone tell me how to get to the admin section working the normal way?



9
toonstruck
Upgrade from 2.013 - 2.2 -- admin.php is blank
  • 2005/8/20 1:17

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


I upgraded from 2.013 to 2.2 and I cannot properly access the admin.php file.

I dont get any errors. I can see the "Xoops" blue bar on top, and then the grey/silver Powered by XOOPS" footer thing. But nothing inbetween. I no longer see the various admin options.

Can anyone help?



10
toonstruck
Re: Cookies (log-in ID) not lasting through a browser close
  • 2005/1/27 3:08

  • toonstruck

  • Just popping in

  • Posts: 12

  • Since: 2004/12/1


Thanks for the link. Unfortunately I gave it a try and it doesn't seem to be working either.. :o ..

I'll have to post a question on that website or something.




TopTop
(1) 2 »



Login

Who's Online

238 user(s) are online (160 user(s) are browsing Support Forums)


Members: 0


Guests: 238


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits