Home › Forums › All Other Themes › Can't upload theme .zip
- This topic has 2 replies, 2 voices, and was last updated 6 years, 3 months ago by Sonl Sinha.
-
AuthorPosts
-
August 11, 2018 at 8:46 pm #105539
How do I install? Trying to upload I get, “Version strings can only contain numeric and period characters (like 1.2). Please fix your Version: line in style.css and upload your theme again.” Trying to install from web, your site wants to charge me again.
Recently purchased and trying install your “fundraiser” theme.
Can’t do much till this happens. I hope I’m not waiting too terribly long.
Thanks in advance,
Kat
Update: I fixed the css file and attempted another upload. This time I got:
Submit Your Theme or Theme Update to the Directory
Your theme will be submitted for review to be distributed on the official WordPress.org Theme Directory.Results of Automated Theme Scanning: Fail
Warning: More than one text-domain is being used in this theme. This means the theme will not be compatible with WordPress.org language packs.
The domains found are complete, tgmpa, themeforce
WARNING: The theme uses the add_shortcode() function. Custom post-content shortcodes are plugin-territory functionality.
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘SKT Events’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘M j, Y @ G:i’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event updated.’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event updated. View item’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event submitted. Preview event’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event scheduled for: %1$s. Preview event’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event saved.’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event restored to revision from %s’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event published. View event’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event draft updated. Preview event’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Event Category’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Custom field updated.’
WARNING: Found a translation function that is missing a text-domain. Function __, with the arguments ‘Custom field deleted.’
WARNING: Found ini_set in the file core-functions.php. Themes should not change server PHP settings.
Line 11: ini_set(‘display_errors’,’Off’);
Line 12: ini_set(‘error_reporting’, E_ALL );
REQUIRED: The theme uses the register_taxonomy() function, which is plugin-territory functionality.
REQUIRED: The theme uses the register_post_type() function, which is plugin-territory functionality.
REQUIRED: Found a Customizer setting that did not have a sanitization callback function. Every call to the add_setting() method needs to have a sanitization callback function passed.
REQUIRED: class-plugin-activation.php. Themes should use add_theme_page() for adding admin pages.
Line 609: $this->page_hook = call_user_func( ‘add_submenu_page’, $args[‘parent_slug’], $args[‘page_title’], $args[‘menu_t
REQUIRED: bloginfo(‘template_url’) was found in the file core-functions.php. Use echo esc_url( get_template_directory_uri() ) instead.
Line 2047: echo bloginfo(‘template_url’);
RECOMMENDED: No reference to add_theme_support( “custom-header”, $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: No reference to add_editor_style() was found in the theme. It is recommended that the theme implement editor styling, so as to make the editor content match the resulting post output in the theme, for a better user experience.
INFO: single.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 8: <?php if( $singletype == ‘single_layout1’){include(‘templates/rightsidebar_single_template.php’);} ?>
Line 9: <?php if( $singletype == ‘single_layout2’){include(‘templates/leftsidebar_single_template.php’);} ?>
Line 10: <?php if( $singletype == ‘single_layout3’){include(‘templates/fullwidth_single_template.php’);} ?>
Line 11: <?php if( $singletype == ‘single_layout4’){include(‘templates/nosidebar_single_template.php’);}?>
INFO: extra.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 199: require_once (ABSPATH . ‘/wp-admin/includes/file.php’);
INFO: enqueue.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 70: require(get_template_directory() . ‘/templates/custom-style.php’);
Line 77: require(get_template_directory() . ‘/templates/custom-javascript.php’);
INFO: customizer.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 4: require(get_template_directory() . ‘/customizer/includes/control-toggle.php
Line 5: require(get_template_directory() . ‘/customizer/includes/control-info.php’)
Line 6: require(get_template_directory() . ‘/customizer/includes/control-editor.php
Line 7: require(get_template_directory() . ‘/customizer/includes/control-multicheck
Line 8: require(get_template_directory() . ‘/customizer/includes/control-radioimg.p
Line 9: require(get_template_directory() . ‘/customizer/includes/helpers.php’);
Line 361: require(get_template_directory() . ‘/customizer/controls/settings-basic.php
Line 362: require(get_template_directory() . ‘/customizer/controls/settings-header.ph
Line 363: require(get_template_directory() . ‘/customizer/controls/settings-frontpage
Line 364: require(get_template_directory() . ‘/customizer/controls/settings-postpage.
Line 365: require(get_template_directory() . ‘/customizer/controls/settings-footer.ph
Line 366: require(get_template_directory() . ‘/customizer/controls/settings-misc.php’
Line 367: require(get_template_directory() . ‘/customizer/controls/settings-shortcode
Line 368: require(get_template_directory() . ‘/customizer/controls/settings-sectionbu
Line 369: require(get_template_directory() . ‘/customizer/controls/settings-code.php’
Line 420: include_once(get_template_directory() . ‘/customizer/extra.php’);Are you sure your theme is compatible with WP? How could I be screwing up such a basic process?
August 12, 2018 at 5:07 pm #105553Close this ticket please.
August 13, 2018 at 11:32 am #105588Okay
-
AuthorPosts
- You must be logged in to reply to this topic.