ShahiLanding

HTML Import Issues

Updated 2 weeks ago 5 7 min read

This guide helps you troubleshoot problems when importing HTML files into ShahiLandin landing pages.

Import Process Fails

Upload Stage Problems

Symptom

Cannot upload HTML file or receive error during file selection.

Problem 1: File Size Too Large

Error Message:
`
The uploaded file exceeds the uploadmaxfilesize directive in php.ini
`

Solution:

  1. Check your server’s upload limit in ShahiLandin → System Info
  2. Your HTML file should be under the upload limit (typically 2MB-64MB)
  3. Reduce file size:

    4. – Remove embedded base64 images
    – Remove unnecessary inline styles
    – Minify HTML before uploading

  4. Increase upload limit:

    5. – Add to .htaccess file:
    `apache
    phpvalue uploadmax_filesize 64M
    phpvalue postmax_size 64M
    `
    – Or contact hosting provider

    Problem 2: Invalid File Type

    Error Message:
    `
    Sorry, this file type is not permitted for security reasons
    `

    Solution:

  5. Only .html and .htm files are accepted
  6. Ensure file has correct extension (not .txt or .zip)
  7. If downloading from source, save as HTML:

    8. – Right-click page → Save As → Web Page, HTML Only

  8. Remove any BOM (Byte Order Mark) from file:

    9. – Open in text editor like Notepad++
    – Convert to UTF-8 without BOM
    – Save

    Problem 3: File Contains Malicious Code

    Error Message:
    `
    File rejected: potentially harmful content detected
    `

    Solution:

  9. ShahiLandin scans for dangerous code:

    10. –
    `

  10. Script execution timing:

    11. - Scripts may run before DOM is ready
    - Wrap code in document ready:
    `html

    `

    Problem 2: Console Errors

    Symptom: Check browser console (F12) and see JavaScript errors.

    Common Errors and Solutions:

    Error: $ is not defined or jQuery is not defined

    • Solution: Load jQuery before your scripts

      • Error: Uncaught ReferenceError: functionName is not defined

    • Solution: Script order issue - load dependency scripts first

      • Error: Mixed Content warnings

    • Solution: Change HTTP links to HTTPS (or remove protocol):

      • `html






      `

      Rendering & Assets Stage Problems

      Asset Mirroring Fails

      Problem 1: Assets Not Downloading

      Symptom: Progress bar stuck or shows "Failed to mirror assets".

      Solution:

    • External domain blocks requests:

      • - Some servers block automated downloads
      - Try manual asset import:
      - Download assets manually
      - Upload to WordPress Media Library
      - Update HTML references

    • Server timeout:

      • - Too many assets or large files
      - Increase PHP execution time in .htaccess:
      `apache
      phpvalue maxexecution_time 300
      `
      - Or import in smaller batches

    • SSL certificate issues:

      • - External site has invalid SSL
      - Temporary fix: Skip asset mirroring for that site
      - Reference assets directly (if allowed)

      Problem 2: Partial Asset Download

      Symptom: Some assets mirror successfully, others fail.

      Solution:

    • Check asset URLs in browser:

      • - Open each failed URL directly
      - Note which ones return 404 or errors

    • For 404 errors: Update URLs to correct paths
    • For permission errors: Contact asset host
    • For large files: Manually upload to Media Library

      • CSS Scoping Issues

      Problem 1: Landing Page Styles Affect Rest of Site

      Symptom: Your landing page CSS changes your theme's appearance.

      Solution:

    • Enable CSS Scoping:

      • - In Step 3 of import wizard
      - Check "Scope CSS to landing page only"
      - ShahiLandin prefixes all selectors with .shahilandin-scope

    • Manual CSS scoping:

      • - Wrap all styles in a unique class:
      `css
      .my-landing-page .container { width: 100%; }
      .my-landing-page .header { background: blue; }
      `

      Problem 2: WordPress Styles Interfere with Landing Page

      Symptom: Landing page looks different than expected due to theme CSS.

      Solution:

    • Use Canvas Mode:

      • - Select rendering mode: Canvas (No Theme)
      - This loads landing page without WordPress theme
      - Most isolated option

    • Increase CSS specificity:

      • - Add !important to critical styles:
      `css
      .container { width: 1200px !important; }
      `

    • Reset WordPress styles:

      • - Add CSS reset at top of your styles:
      `css
      .shahilandin-content * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
      }
      `

      Review Stage Problems

      Preview Doesn't Match Original

      Problem 1: Fonts Look Different

      Symptom: Text appears in wrong font family.

      Solution:

    • Web fonts not loaded:

      • - Import Google Fonts or custom fonts:
      `html`

    • Font files not mirrored:

      • - Enable asset mirroring
      - Or upload font files to WordPress
      - Reference via CSS:
      `css
      @font-face {
      font-family: 'CustomFont';
      src: url('/wp-content/uploads/fonts/custom.woff2');
      }
      `

      Problem 2: Colors Are Different

      Symptom: Background colors, text colors don't match original.

      Solution:

    • CSS not fully extracted:

      • - Check if inline styles present:
      - ShahiLandin extracts