Title: Parse errrorr Last modified: August 19, 2016 --- # Parse errrorr * Resolved [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/) * Can someone advise please? * Can’t view site. Custom design. * [http://www.kjzrradio.com](http://www.kjzrradio.com) * Thank you Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/topic/parse-errrorr/page/2/?output_format=md) [→](https://wordpress.org/support/topic/parse-errrorr/page/2/?output_format=md) * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532014) * Did you alter the Default theme’s Page template at all? * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532016) * I never mess with the default theme. * Would you care to view page.php code? * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532019) * If you didn’t alter the code, there’s no reason to see it. * The first thing to do would be to rule-out a plugin or theme-specific issue. * 1. Reset your plugins following this guide: * [http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F](http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F) * If that resolves the issue, reactivate each one individually until you find the cause. * 2. Use an [FTP or SFTP client](http://codex.wordpress.org/FTP_Clients) and navigate to `/wp-content/themes/` and rename every directory **except** the `/classic/` directory. This will force the Classic theme to activate. If that works, then [download WordPress](http://wordpress.org/download/) again and upload a new copy of the `/wp-content/themes/default/` directory. * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532022) * Tried resetting the plugins. * No go. * I did re-set file permissions (chmod) at server in wp-content. * Would that have effected viewing? * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532028) * That’s possible. Directories should be 755 or 777 for write permissions and files should be 644 or 666 for write permissions. * Did you rule-out a theme-specific problem? * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532031) * Sorry macmanx. * How do I determine theme specific problem? * If I recall, (been a long day) things changed after file permissions were reset. * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532033) * Follow step 2 in my earlier reply. * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532035) * Upon viewing the Manage Themes area, we see this: * Warning: uksort() [function.uksort]: The argument should be an array in /data/ 19/1/56/51/1871703/user/2033523/htdocs/www/wp-admin/themes.php on line 65 * Warning: array_slice() expects parameter 1 to be array, boolean given in /data/ 19/1/56/51/1871703/user/2033523/htdocs/www/wp-admin/themes.php on line 86 * Warning: array_keys() [function.array-keys]: The first argument should be an array in /data/19/1/56/51/1871703/user/2033523/htdocs/www/wp-admin/themes.php on line 174 * Warning: natcasesort() [function.natcasesort]: The argument should be an array in /data/19/1/56/51/1871703/user/2033523/htdocs/www/wp-admin/themes.php on line 175 * What do you suggest please? Thanks * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532037) * Please follow step 2 from my earlier reply to rule-out a theme-specific issue. * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532039) * Will custom design still be available after fix? * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532057) * You’re just changing the directory names, so your customizations will remain in tact. You can change the directory names back when you’re done. * According to the error: * `Parse error: syntax error, unexpected $end in /data/19/1/56/51/1871703/user/ 2033523/htdocs/www/wp-content/themes/default/page.php on line 929` * The problem may be coming from the Default theme. If your “custom design” is a modified Default theme, then “I never mess with the default theme” is not entirely true, and you will lose customizations if you have to replace those files. * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532147) * macmanx- Followed your steps to the letter. * No joy. * Still getting the same error. * [http://www.kjzrradio.com](http://www.kjzrradio.com) * Server side shows site is up. * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532155) * When I navigate to error: * htdocs/www/wp-content/themes/default/page.php on line 929 * Viewing the source code reveals only 755 lines not 929. * Does this make sense to anyone? * Moderator [James Huff](https://wordpress.org/support/users/macmanx/) * (@macmanx) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532157) * That’s because the source is also displaying code generated by `page.php` . * Try this: * 1. Make a backup copy of `/wp-content/themes/default/` (use your FTP client to download the directory). * 2. Delete `/wp-content/themes/default/` from the server. * Is the error gone? * Thread Starter [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * (@kjzrradio) * [16 years ago](https://wordpress.org/support/topic/parse-errrorr/#post-1532169) * Can I rename it instead of deleting it? Viewing 15 replies - 1 through 15 (of 21 total) 1 [2](https://wordpress.org/support/topic/parse-errrorr/page/2/?output_format=md) [→](https://wordpress.org/support/topic/parse-errrorr/page/2/?output_format=md) The topic ‘Parse errrorr’ is closed to new replies. ## Tags * [parse-error](https://wordpress.org/support/topic-tag/parse-error/) * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/) * 21 replies * 2 participants * Last reply from: [kjzrradio](https://wordpress.org/support/users/kjzrradio/) * Last activity: [16 years ago](https://wordpress.org/support/topic/parse-errrorr/page/2/#post-1532188) * Status: resolved ## Topics ### Topics with no replies ### Non-support topics ### Resolved topics ### Unresolved topics ### All topics