Created a theme and can't get it to work now.

What “extra” stuff did you add to your functions.php file on your theme?

I’ve heard rumors of zipped files getting corrupted (I think specifically on GoDaddy) when uploaded via the WP admin. If you can upload the files directly to your /wp-content/themes/ folder, try that.

If that doesn’t help answering Jorge’s question will help people troubleshoot.

I only upload via ftp …

as for the function file, I added a bunch of stuff..

It’s working perfectly on my localhost thou ..

Please verify that you have a style.css file in your theme folder:

wp-content/themes/eliteearnerstheme/style.css

If the file does not exist, WordPress wont be able to load the theme information, hence, it wont be activated. The file must exists within your theme folder and it must contain the theme information as stated here:

https://codex.www.ads-software.com/Theme_Development#Theme_Stylesheet

@cashmunkey

First, having a bunch of stuff on your functions.php file may not be causing the errors – but make sure that all of your functions are properly coded with open and closed brackets. DOCUMENT YOUR WORK EVEN IF YOU’RE THE ONLY LIVING SOUL TO EVER LOOK AT THE WORK – even comment on the small lines of code so when you go back you can see what you’re doing. That’s one of my 2012 resolutions. This has helped me especially when tracking bugs.

From your descriptions, I believe either your functions.php file has incomplete/buggy code OR the charset on the file itself is not supported after you upload to your production host. WITH THAT SAID…

What charset did you use to edit your functions.php file? You might think it’s UTF-8, but to be specific: is it Windows/UTF-8 or Unix/UTF-8? That too plays a big roll in errors when uploading from localhost to a production host.

I use Notepad++ on Windows7 but always make sure the charset is Unix/UTF-8 as Windows ANSII/UTF-8 would produce unexpected lines of text or errors like you described.

Hope this helps.

JORGE. I have no clue man.
We just uploaded to bluehost.com and it works. Seems to be a godaddy issue. I can’t figure it out .. and the dude from ODESK is lost too I think .. Ha.

Code in Function.php which is creating issues.
Error Code:

// Load TinyMCE Plugin
require_once(eetheme_ADMIN . '/tinymce/tinymce.php');
// Load Custom Shortcodes
require_once(eetheme_FUNCTIONS . '/shortcode.php');

Works when code is :

// Load TinyMCE Plugin
//require_once(eetheme_ADMIN . '/tinymce/tinymce.php');
// Load Theme Functions
//require_once(eetheme_FUNCTIONS . '/theme-functions.php');
// Load Custom Shortcodes
require_once(eetheme_FUNCTIONS . '/shortcode.php');

————————————————————

This is the tinymce.php file.

[Code moderated as per the Forum Rules. Please use the pastebin]

This is the Function.php

[Code moderated as per the Forum Rules. Please use the pastebin]

JORGE. I have no clue man.

Er, I made a mistake in explaining it before. Let me clarify.

If this were happening to me, I’d first check the functions.php encoding – especially since the development is on one environment and sent to production on another environment and the two environments may use different encoding to read/execute files.

To find out a generic encoding on various environments – that works and has been tested since the dawn of WordPress – I look no further than Hello Dolly. Simply open Hello Dolly in your text editor (I’m going to describe as if using Notepad++) and look to see if the encoding is displayed on the window. For Hello Dolly, it should read UNIX ANSI.

Go back to your functions.php file on your theme using the same editor and verify the encoding. I’ve experienced problems with plugins and the functions.php file when the files used are encoded with DOS\WINDOWS UTF-8, DOS\WINDOWS ANSI, UNIX UTF-8, etc. I verified the results after some more testing and keeping the encoding to UNIX ANSI corrected the errors.

I realize that I may not be explaining this as well however, this experiment would result in similar errors as described from your first post.

I hope this helps.