[serkan]

Hi Markus,

Thank you for your question. If you’d like to use only a specific page (for example, the Home page from Demo 11) as a template inside your current installation with Demo 13, here’s the easiest way:

Create a new blank page in WordPress.

Edit the page with Elementor.

In the Elementor editor, click on the “Add Template” button.

Go to the “My Templates” tab — here you will see the demo pages that came with the theme.

From this list, you can insert the Home page of Demo 11 (or any other demo page) directly into your new page.

This way, you can freely mix and match — importing only the landing page (or even sections) you want, without reinstalling another full demo.

👉 Tip: Once imported, you can also save individual sections as Elementor templates, so you can reuse them quickly when building additional landing pages.

Best regards,
Serkan

[serkan]

Hello,

Thank you for reaching out. Since the TutorLMS Pro license was registered under our developer account (and not under your personal account), you won’t be able to access direct support from their team.

Don’t worry — if you encounter issues (like Zoom integration), you can let me know here and I’ll help you troubleshoot or, if needed, reach out to the plugin provider on your behalf.

👉 Please share the exact problem/error you’re experiencing when trying to connect Zoom, and I’ll check the settings and guide you step by step.

Best regards,
Serkan

[serkan]

ello,

Thank you for your message and for explaining your goal so clearly.

Just to clarify: Podkest is only a theme, so it displays the content that already exists in your WordPress posts (titles, descriptions, featured images, embeds, etc.). The actual import of podcast episodes from your RSS feed (including descriptions, per-episode images, tags, and external players) is handled by plugins.

We haven’t officially tested the theme with advanced RSS import plugins, so we cannot guarantee full compatibility. That said, here are some commonly used solutions you may want to explore:

Seriously Simple Podcasting (SSP) → it has a built-in RSS importer, but depending on the feed, sometimes only titles are imported.

Option A — Try with Seriously Simple Podcasting (SSP)

Install/activate Seriously Simple Podcasting.

Go to Podcasting → Tools → Import from RSS (or “Migrate”).

Paste your Ausha RSS URL.

In the importer options, enable:

Import description/content (itunes:summary).

Import episode image as Featured Image (from itunes:image).

Import categories/tags (map RSS categories to WP categories/tags).

Do not download/host MP3 files (keep external hosting).

Run the import.

For the player, paste each Spotify or Ausha episode URL on its own line in the episode content — WordPress will auto-embed supported players. (If you prefer Ausha’s iframe, paste their embed code into the content.)

If SSP only imports titles for your feed, it usually means the RSS isn’t exposing the description/image fields in the way SSP expects.

Podcast Importer SecondLine or WP All Import (Pro) with the RSS add-on → these allow field mapping (title, description, episode image, tags, external player link).

Option B — Use a dedicated RSS importer with field mapping (recommended if SSP is partial)

If SSP doesn’t bring in descriptions/images/tags as needed, use an RSS importer that lets you map fields:

Install a podcast RSS importer that supports field mapping (e.g., “Podcast Importer SecondLine” or a flexible importer like WP All Import (Pro) + RSS add-on).

Choose Post Type = your podcast episodes (SSP’s episode post type) or regular Posts if you don’t use SSP.

Map fields:

title → Post Title

itunes:summary / description → Post Content

itunes:image → Featured Image

category → Categories/Tags

episode link (Spotify/Ausha) → put the URL into the content template so the player appears automatically (auto-embed), or insert Ausha’s iframe embed.

Run the import (140+ episodes). If your host has strict limits, import in batches (e.g., 50–60 items per run) to avoid timeouts.

After import

Set your podcast/archive page and menus as desired; the theme will display the featured image, content, tags, and any embedded player.

If any episode is missing a cover, check whether the feed includes itunes:image for that item; if not, configure the importer to use the first image in content or a fallback.

With either approach, once the episode posts are correctly imported, the Podkest theme will display them as designed (title, description, featured image, player embed, categories/tags).

👉 Since this is more of a plugin/import function than a theme feature, we recommend testing with your feed on a staging site first. If you share your Ausha RSS feed, we can also have a look at what fields it contains and point you toward the right mapping.

Best regards,
Serkan

[serkan]

Hello @casabella
I’ve just checked your website and the homepage slider is now displaying correctly — it seems the issue has been resolved. 👍

Sometimes these kinds of problems can happen due to caching or third-party plugins (such as cache/optimization plugins) rather than the theme itself.

👉 If you notice this again in the future, I recommend temporarily deactivating non-theme plugins, clearing your cache, and then checking the site. This usually fixes such display issues.

Please feel free to reach out if you need further assistance.

Best regards,
Serkan

[serkan]

Hello Stefi,

Thank you for letting us know, and no worries at all — I’m glad to hear you found the cause and that everything is working correctly now.

If you ever need any assistance related to the theme itself, please feel free to reach out and I’ll be happy to help.

Best regards,
Serkan

[serkan]

Good evening,

Yes, that is possible. You can activate the theme on your temporary development/staging domain to build the site. Once you’re ready to go live, you can deactivate the license on the temporary domain and then reactivate it on the final domain without any issues.

If you run into any problems during reactivation, just let us know and we’ll be happy to assist.

Best regards,
Serkan

[serkan]

Hello,

Thank you for the update. I’m glad to hear that you were able to solve the issue so clearly and easily with those steps. Great job!

If you need any further assistance or adjustments in the future, feel free to let me know — I’ll be happy to help.

Best regards,
Serkan

[serkan]

Hi DerPatschen,
Thanks for the feedback.

[serkan]

Hi DerPatschen,
Thanks for the feedback.

[serkan]

Hi DerPatschen,
Thanks for the feedback.

[serkan]

Hi,
Yes, you can also do this directly in Elementor without adding custom CSS. When you edit the gallery widget (or the image inside the masonry grid):

Select the Image / Gallery widget.

Go to the Style tab.

Look for the Border Radius setting.

Adjust the radius (e.g., 12px) until you see the rounded corners you like.

⚠️ However, in some gallery layouts (especially masonry grids), Elementor may not apply the border radius to the images because of how the gallery plugin handles the image containers. In that case, a small CSS snippet (like the one I sent before) will be the most reliable solution.

So:

Try the Elementor “Border Radius” first.

If it doesn’t affect the gallery images, then add the CSS.

.elementor-lightbox .elementor-lightbox-image { border-radius: 15px; }

Thanks

[serkan]

Good evening,

Yes, that is possible. You can activate the theme on your temporary development/staging domain to build the site. Once you’re ready to go live, you can deactivate the license on the temporary domain and then reactivate it on the final domain without any issues.

If you run into any problems during reactivation, just let us know and we’ll be happy to assist.

Best regards,
Serkan

[serkan]

Hi,

Thank you for sharing the screenshot and the website link. I’ve reviewed the issue, and it looks like a rendering/visual glitch that happens while scrolling. This could be caused by CSS styles, browser-specific rendering, or a conflict with the theme/animations.

For clarification, I’d like to mention that this issue does not appear on MacBook devices using Safari or Chrome. Could you please confirm which browser(s) and device(s) you’re experiencing this on? It will help me reproduce the issue and apply the right fix on the live site.

Once I have that info, I’ll troubleshoot further and resolve it as soon as possible.

Best regards,
Serkan

[serkan]

Hello,

I have securely logged into your website and checked the hosting/server settings. As I mentioned earlier, our themes require the following minimum system requirements, which are listed here:
👉 https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/

Required values:

WordPress version: 6.2 or higher

PHP version: 8.0 or higher

PHP time limit: 300

PHP memory limit: 1024M

Max input time: 1500

Upload max filesize: 128M

PHP post max size: 256M

When I checked your current server values from WP Admin > Tools > Site Health > Info > Server, I saw the following:

PHP time limit: 165 (should be at least 300)

PHP memory limit: 512M (should be at least 1024M)

Max input time: -1 (requirement: 1500)

PHP post max size: 130M (should be at least 256M)

These differences may prevent the demo import from working properly. I had shared this requirements link with you earlier, but it seems the values were not fully adjusted yet.

👉 Could you please contact your hosting provider and ask them to update these values to meet the theme requirements?
After these adjustments, the demo import should work correctly. If you prefer, once the hosting settings are updated, you can let me know and I can help you complete the demo installation.

Best regards,
Serkan

[serkan]

You are welcome :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Hi, I cannot view any of your personal information. There is a private content box below. If you write in that area along with your message, you can create your message in a secure area that only we can view.
Thanks

[serkan]

Hello,

Thank you for your message.

First, please make sure that your hosting/server environment meets all the system requirements for our WordPress themes. Sometimes missing requirements (like PHP version, memory limit, or execution time) can prevent the demo from importing correctly.

If you still experience issues after checking this, please share your WordPress admin login details and site URL inside the Private Content Box here in the support forum. That way, we can log in securely and help you install and configure the Home 05 demo for you.

Looking forward to your update.

Best regards,
Serkan

[serkan]

Hi,
Could you try to use this custom css code;

@media (max-width: 768px) { 
.is-header-small .site-header .site-title a { margin-left: 40px; } }

The main Projects (portfolio archive) and News (blog archive) pages, however, are not editable directly in Elementor because they are generated by the theme’s template. To customize those layouts, you’ll need to go to Appearance → Customize → Portfolio (for Projects) or Appearance → Customize → Blog (for News). From there you can adjust how those sections look and display.

If you’d like to have full Elementor control over those pages, the workaround is to create a new static page (e.g. “My Projects” or “My News”), design it with Elementor, and then link to it instead of the default archive page.

This way you can use Elementor for the individual items, and the Customizer for the overall archive layout.

Thanks

[serkan]

Hi Stefi,
Thank you for reaching out and for providing the details.
A few steps you can try:

Clear cache: If you are using a caching plugin or server-side cache, please clear it and test again.

Database check: Go to Amelia → Settings → General and look for the option to “Check/Repair database” (if available). This can re-align tables with the latest version.

Deactivate/Reactivate plugin: Deactivate the Amelia plugin, then reactivate it to re-initialize connections.

Reinstall plugin: If the issue persists, delete the plugin files (do not delete Amelia data) and reinstall the latest version from your account/download.

Known issue: The error message looks related to the new ProviderRepository introduced in recent versions, so it may also be a bug. If the above steps don’t resolve it, let u know and we can open a support ticket directly with Amelia so they can confirm if it’s a known issue in the latest release.

👉 To be safe, please make a full backup of your site and database before running the repair or reinstall steps.

Let me know how it goes, and if the error continues, I’ll help you gather the logs and escalate it further.

Best regards,
Serkan

[serkan]

Hi @psanch

Thanks for the details and screenshots. Let me clarify how this works with the theme:

Portfolio items (Projects) and Blog posts can be opened and edited individually with Elementor. When you open a single project or blog post, you should see the “Edit with Elementor” option.

The main Projects (portfolio archive) and News (blog archive) pages, however, are not editable directly in Elementor because they are generated by the theme’s template. To customize those layouts, you’ll need to go to Appearance → Customize → Portfolio (for Projects) or Appearance → Customize → Blog (for News). From there you can adjust how those sections look and display.

If you’d like to have full Elementor control over those pages, the workaround is to create a new static page (e.g. “My Projects” or “My News”), design it with Elementor, and then link to it instead of the default archive page.

This way you can use Elementor for the individual items, and the Customizer for the overall archive layout.

Hope this clears things up! Let me know if you’d like me to walk you through creating a custom page as an alternative.

Thanks,
Serkan

[serkan]

Hi,
That message appears because the theme templates for “Projects” and “News” are not calling the the_content function, so Elementor can’t hook into them directly.

Go to Elementor > Settings > General in your WordPress dashboard.

Make sure the boxes for Posts, Projects (Portfolio), or any custom post types you want to edit are enabled.
Then try opening those items again in Elementor.

Thanks

[serkan]

Hello 👋

Before switching demos, please first export/backup your current content from Tools → Export → All content. Then, if you’d like a specific demo, you can import it, and afterwards re-import your own posts/pages. Please note that switching demos is not one-click; each demo has a different design and needs to be set during the first import.

You can customize the theme via Appearance → Customize.

➡️ About the pink area behind the logo: if you share your WP Admin login details with us inside the Private Content box, I can check and fix it directly for you.

Thanks

[serkan]

Hi, no worries at all, thank you for letting us know — we’re glad to hear everything is now working fine on your new server.

We’d be very happy if you could spare a minute to rate the theme on ThemeForest. Your feedback really boosts our motivation and helps us work harder on future updates.

👉 https://themeforest.net/downloads

Thank you so much for your support!

Best regards,
Serkan

[serkan]

Hi, thanks for checking that and for your follow-up.

Reinstalling the theme will not affect your content (posts, pages, or statistics) — those are all stored in your WordPress database, so your blog visits will remain intact.

Your plugins will also stay installed. However, since TheBlogger theme comes with its own companion plugins, after reinstalling you may be asked to re-activate or update those theme plugins. Don’t worry — your plugin data and settings will still be preserved.

As always, I recommend taking a full backup (files + database) before proceeding, just to be safe.

Best regards,
Serkan

[serkan]

Hi @andremaajin

Thank you for sharing these details and for clarifying your workflow concerns — that’s very helpful for us to understand.

Since your setup involves more than 600 existing PowerPress episodes, we believe the best way forward is to have our developer review this case directly and advise you on possible solutions. This will ensure you receive accurate, tailored guidance without the risk of disrupting your current library.

I’ve forwarded your feedback and request to our development team, and they will get back to you with the most suitable approach.

Thanks again for your patience and for raising these important points.

Best regards,
Serkan

[serkan]

Hi @Aniket

Thanks for letting us know. Sometimes, depending on the server limits or how the demo import process runs, certain sections (like the Hero section in Home 6) may not be imported automatically.
https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/
Please check it out.
Thanks

[serkan]

Yes, that’s correct — the CSS we provided will only affect the mobile view.

[serkan]

Hi @andremaajin

Thank you for your detailed message and for choosing the Podkest theme.

The theme is designed to be compatible with PowerPress, but the Podkest player does not automatically override the default PowerPress player. Instead, you need to:

How to use the Podkest player instead of the PowerPress one:

In PowerPress > Settings > Appearance, uncheck the option that outputs the default PowerPress player in your posts (Display Player).

Then, edit your podcast post and make sure you add your audio file (mp3, etc.) using the theme’s audio field (in the Audio Post Format). The Podkest player will appear when the audio file is entered here.

If PowerPress is still injecting its own player, it means it’s forcing the shortcode output. In this case, you’ll need to disable that option inside PowerPress so the theme’s player can render instead.

👉 Here is our documentation
https://docs.pixelwars.org/podkest.php
, and you can also compare with the demo site
https://themes.pixelwars.org/podkest/demo-01/
to see how the player is expected to look.

At the moment, since you didn’t share your site URL, I can’t confirm if something else (like caching, plugin conflict, or PowerPress settings) is interfering. Could you please share the link to one of your podcast posts? That way we can inspect the front-end and provide precise instructions.

I also want to acknowledge your feedback about documentation and plugin details — thank you, we’ll improve that part for future updates.

Best regards,
Serkan

[serkan]

Hi Stefi,

Thank you for reaching out. The issue you are experiencing with Google Calendar integration in Amelia is not related to the Efor theme. The theme does not interfere with or limit plugin-to-Google API connections.

Google Calendar integration in Amelia depends on:

Correct Google API credentials (Client ID, Client Secret, Redirect URI) being set up in the Google Cloud Console.

The server meeting Amelia’s requirements (PHP version, cURL, allow_url_fopen, OpenSSL enabled, etc.).

Proper database connection (the wp_amelia_providers_to_google_calendar table is part of Amelia, not the theme).

👉 I recommend:

Double-checking that the Redirect URI in your Google Cloud Console project exactly matches the one listed in Amelia’s documentation.

Ensuring your hosting environment has all the required PHP extensions enabled.

If the issue persists, contacting Amelia’s support directly, as they can assist with debugging API authorization errors more precisely.

Since this integration is entirely handled within Amelia, there is no known compatibility issue with the Efor theme.

If you have trouble getting in touch with Amelia’s support team, please let us know — we’ll be happy to assist you in establishing communication with them.

Best regards,
Serkan

[serkan]

Hi,

Thanks for sharing the details. I’ve carefully checked your server values from Site Health, and compared them with our recommended requirements:

Your current server values:

PHP time limit: 30 (required: 300)

PHP memory limit: 256M (required: 1024M)

PHP max input time: -1 (recommended: 1500)

Upload max filesize: 100M (recommended: 128M)

PHP post max size: 100M (recommended: 256M)

https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/

As you can see, the hosting environment is currently far below the recommended limits for running the Efor theme demos smoothly—especially the PHP time limit and memory limit, which directly affect page loading and large demo content like Demo #13.

These limits are managed by your hosting provider (not the theme itself). When they are too low, it results in exactly the issues you’re describing: slow loading, images failing to appear on the first load, and pages requiring a refresh.

👉 To resolve this, please ask your host to increase the values at least to:

PHP time limit: 300

PHP memory limit: 1024M

PHP post max size: 256M

Upload max filesize: 128M

Max input time: 1500

Once your host updates these values, the demo should run normally and load as expected.

Let us know after these adjustments are made so we can recheck together.

Best regards,
Serkan

[serkan]

Hi,

Thank you for your feedback.

The issue with demo import may be related to your PHP configuration. Currently, your server has max_input_time set to 300 seconds. This value may be insufficient for larger demo packages and can cause the import to stop before it completes. Our developer recommends increasing it to 1500 seconds to ensure the demo content can be fully processed.
https://www.pixelwars.org/forums/topic/system-requirements-for-wordpress-themes/

Also, when I tried to import the demo import, I noticed that the Efor theme is not installed on your site. In order to proceed with the Efor demo installation, please upload and activate the Efor theme under Appearance > Themes, and then let me know once it’s in place so I can continue the setup.

Best regards,
Serkan

[serkan]

Thanks for the feedback :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Hi @Square-Egg

Thank you for reaching out and sharing the details.

I checked the issue you described. Since the email addresses display correctly in Brave but not in Chrome or Edge, this suggests it may be related to browser rendering or a CSS/JavaScript conflict rather than a plugin update.

Here are a few steps you can try:

Clear browser cache in Chrome/Edge and check again.

Inspect the email text with Developer Tools (F12) to see if there are any inline styles (e.g., display:none, visibility:hidden, or special character encoding) being applied.

Check your child theme CSS/JS files – sometimes custom CSS or minification can affect how certain text (like email addresses) is displayed.

Temporarily switch to the parent theme to see if the issue persists. If it works fine, the issue is coming from the child theme customization.

Check if your hosting has email address obfuscation enabled (some security or antispam features automatically hide email addresses in certain browsers).

Could you please try switching to the parent Archy theme (just for testing) and let me know if the problem remains? That will help us narrow down if the issue is from the child theme.

Once we confirm that, I’ll guide you on the exact fix.

Best regards,
Serkan

[serkan]

Hi,
Please provide me your wp admin details via our private content box below?
Thanks

[serkan]

Hi,
I’m glad to hear that you were able to log in successfully this time. 😊 Sometimes there can be temporary glitches with the Envato/ThemeForest validation system, but now that it’s working, you shouldn’t have any issues going forward.

If the purchase code error happens again, please feel free to let me know and I’ll assist you right away.

Best regards,
Serkan

[serkan]

Hi,
Thanks for the details. The “smooth scroll” option controls the page scrolling, not the homepage “Scrolling Gallery” template., unfortunately, this is not available by default, and modifying source files is out of our support scope.

Have a nice day!

[serkan]

Hi, unfortunately, this is not available by default, and modifying source files is out of our support scope.

Have a nice day!

[serkan]

Hi,
I will forward this request to our developer and i will keep you updated.
Thanks

[serkan]

Hi,
Please go to appearance > customize > header > general > header layout (you can only choose one of our layout). It is not possible by default.
Thanks

[serkan]

Hi,
You can go to appearance > customize > site identity > you can increase the logo size for the mobile here.
You need to write a lot of css code to make the Hamburger icon bigger. Because each line is managed with css code in itself.
Thanks

[serkan]

Thanks for the feedback :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Thanks for the feedback :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

You are welcome :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Hi B,

You can increase the navigation bar size on mobile by adding a small CSS adjustment:

Go to Appearance → Customize → Additional CSS.
Paste this code:

@media (max-width: 768px) {
    .site-header, 
    .main-navigation {
        height: 70px; /* Increase the height */
    }
    .main-navigation a {
        font-size: 18px; /* Increase menu text size */
        padding: 15px;   /* Increase clickable area */
    }
}

Click Publish to save.

You can adjust the height, font-size, and padding values until it feels comfortable on your mobile menu.

Thanks

[serkan]

Hi,
You can check out the documentation
https://themes.pixelwars.org/doc/read/#shortcodes
Thanks

[serkan]

You are welcome :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Hi,
Thank you for reaching out. I’ve compared your site with our demo, and I’m not seeing any issues with the fonts or stuttering. The CSS seems to be properly loaded in the demo site, and everything appears to be functioning smoothly.

Here are a few things to check:

Clear Browser Cache:

Sometimes, cached files can cause the site to display incorrectly. Try clearing your browser cache or open your site in an incognito window to see if the problem persists.

Plugin Conflict:

Disable any third-party plugins temporarily to check if any of them might be causing conflicts with the theme’s CSS.

Check for Missing Files:

Ensure that all the necessary theme files were uploaded properly. Sometimes, a file might be missing or corrupted during the installation process.

Custom CSS/Theme Customizer Settings:

If you’ve made any customizations or changes via the theme customizer, these might interfere with the default layout. You could reset to default settings to check if that resolves the issue.

Let me know how it goes or if you’d like further assistance.

Best regards,
Serkan

[serkan]

Hi,
You can use this custom css code;

.blog-grid.first-full .hentry:first-child .hentry-middle { max-width: none !important; }

Thanks

[serkan]

You are welcome :) We’d be very happy if you can spare a minute to rate the theme on ThemeForest. Your feedback will boost our motivation and help us to work harder on future updates.

https://themeforest.net/downloads

Thank you for your support.

[serkan]

Hi there,

Thank you for your detailed explanation — and great job narrowing down the issue!

Based on what you described, it appears the current issue is due to a version mismatch between Tutor LMS core (3.7.1) and Tutor LMS Pro (3.7.0). These two components must always be on compatible versions to work correctly together.
You’re currently using:

Tutor LMS Free: ✅ 3.7.1 (latest)

Tutor LMS Pro: ❌ 3.7.0 (older version)

This version mismatch is causing the error. Once you update Tutor LMS Pro to version 3.7.1, the issue should be resolved.

You can request License key Tutor LMS Pro via our official support page here:
👉 https://www.pixelwars.org/forums/topic/tutorlms-pro/

In the meantime, you can safely leave Tutor LMS Pro disabled to maintain site functionality, as you’re already doing.

Best regards,
Serkan