Cchost/guide/Troubleshooting - Revision history

Fourstones: /* Blank Screen On Upload */

2009-06-12T18:39:47Z

‎Blank Screen On Upload

2009-05-08T21:57:58Z

‎IE8 Layout Issues

2009-05-08T21:54:13Z

‎IE8 Layout Issues

2009-05-08T21:53:50Z

‎IE8 Layout Issues

2009-05-07T16:53:30Z

‎File Access

2009-05-04T22:43:02Z

‎Blank Screen On Upload

2009-05-03T19:57:51Z

‎Blank Screen On Upload

2009-05-03T19:56:23Z

blank screen on upload

2009-04-23T22:09:55Z

new SF permalink for bug tracking

2009-04-15T19:02:54Z

‎IE8 Layout Issues

@@ Line 13: / Line 13: @@
 The most common reasons have to do with [[CcHost_File_Access|file access conflicts]] in Apache as well as memory allocation and other settings in your PHP configuration.
-For ccHost 5.1 (in SVN only as of this writing) you can check your installation by browsing to ''/ini_settings''.
+For ccHost 5.1 you can check your installation by clicking on ''Global Settings'' then ''Check PHP Settings'' (or browsing to '''/ini_settings''').
 Otherwise these settings should be sufficient:
@@ Line 70: / Line 70: @@
 If the upload did ''not'' succeed then the problem is definitely in your operating system or PHP environment and not in ccHost.
-If the upload did succeed there might be a problem with you getID3 installation. To test that possibility you'll need to edit a file within the ccHost installation called '''cchost_lib/cc-fileveryify.php''' In that file at about line 143 there is a line of code that looks like:
+If the upload did succeed there might be a problem with your getID3 installation. To test that possibility you'll need to edit a file within the ccHost installation called '''cchost_lib/cc-fileveryify.php''' In that file at about line 143 there is a line of code that looks like:
          <nowiki>CCDebug::QuietErrors();
@@ Line 86: / Line 86: @@
 Now try your upload using the ccHost submit forms. If there is a problem with your getID3 installation, then the errors should lead you to what the solution is.
 = IE8 Layout Issues =

@@ Line 101: / Line 101: @@
 If you don't see an 'extra-meta' field you can add one:
-# Browse to admin/tempaltetags/new
+# Browse to admin/templatetags/new
 # Type '''extra-meta''' into the field and submit

@@ Line 102: / Line 102: @@
 # Browse to admin/tempaltetags/new
-# Type '''extra-meta''' into field and submit
+# Type '''extra-meta''' into the field and submit
 That should return you to the template tags editing screen where you can add the meta tag above.

← Older revision		Revision as of 21:53, 8 May 2009
Line 98:		Line 98:

	<nowiki><meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /></nowiki>		<nowiki><meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /></nowiki>
		+
		+	If you don't see an 'extra-meta' field you can add one:
		+
		+	# Browse to admin/tempaltetags/new
		+	# Type '''extra-meta''' into field and submit
		+
		+	That should return you to the template tags editing screen where you can add the meta tag above.

	= File Access =		= File Access =

@@ Line 102: / Line 102: @@
 By far the most common issue with new installs on Unix based systems involves file access permissions. The recommended way of dealing with this is to set the entire ccHost directory structure as all-access (0777) just while you get things going. If everything else is working then you should follow the
 [[CcHost_File_Access|ccHost file access guildlines]].
 = Outputting Debug Messages =
 Debug messages are special messages that help ccHost developers troublshoot your site when there is a problem. The option to turn on debug message output is '''on''' by default in 5.0 installations and upgrades. The file that controls this option is <nowiki><your_local_files>/lib/DEBUG.php</nowiki>. You can remove this file (or change the extension to something other than .php) and that will turn the option '''off''' debug output for your production site.

← Older revision		Revision as of 22:43, 4 May 2009
Line 78:		Line 78:

	<nowiki>// CCDebug::QuietErrors();</nowiki>		<nowiki>// CCDebug::QuietErrors();</nowiki>
		+
		+	A few lines later do the same thing to the ''RestoreErrors'' calls so it looks like:
		+
		+	<nowiki>// CCDebug::RestoreErrors();
		+	</nowiki>
		+

	Now try your upload using the ccHost submit forms. If there is a problem with your getID3 installation, then the errors should lead you to what the solution is.		Now try your upload using the ccHost submit forms. If there is a problem with your getID3 installation, then the errors should lead you to what the solution is.

@@ Line 8: / Line 8: @@
 = Known Issues =
 Please consult our [http://sourceforge.net/tracker/?func=browse&group_id=80503&atid=559966&status=1&category=751589 bug tracker] for the latest list of unresolved issues.
 = IE8 Layout Issues =

@@ Line 7: / Line 7: @@
 {{lowercase}}
 = Known Issues =
-Please consult our [https://sourceforge.net/tracker/?atid=559966&group_id=80503&func=browse bug tracker] for the latest list of unresolved issues.
+Please consult our [http://sourceforge.net/tracker/?func=browse&group_id=80503&atid=559966&status=1&category=751589 bug tracker] for the latest list of unresolved issues.
 = IE8 Layout Issues =
 Some of the screens in some of the skins are problematic for Internet Explorer 8.