[Mehmet S.]

Hi @lfkconsulting,

Done. Your footer text color wasn’t set yet, so it was inheriting the dark body text color (#3f3f3f), which is almost invisible on your dark footer background (#121212).

I set both “Footer Text Color” and “Copyright Bar Text Color” to #ffffff under Appearance > Customize > Footer, and published the change. The widget titles, text, menu links and the copyright line in the footer are now white. You can adjust these two colors anytime from the same place.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for the details. We checked your site and found the cause.

On screens narrower than 960px the theme switches to its “safe mode” layout. In that mode the script that switches between the book’s pages also runs on regular WordPress pages such as /epk/, and it hides the page content there. That’s why you see the header and the background but no content. The front page is the book itself, so it isn’t affected.

This is a theme bug, not something wrong with your site. We will release a theme update that fixes it within a week. Once it’s out, update the theme and the page content will show on mobile again.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Glad to hear it is solved, and thank you for letting us know the cause. A full database explains everything we saw: Elementor could not save the data it uses to track its CSS files, so the files and the database went out of sync after every change.

To prevent it from happening again, check the database size in Hostinger hPanel from time to time and keep post revisions and expired transients under control (a cleanup plugin such as WP-Optimize can do this on a schedule).

Since this issue has been resolved, we’re closing this topic to new replies. If you need any further help, please feel free to open a new topic and include a link to this one so we can pick up where we left off.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @ammar,

I checked your site: it is running Efor 13.3.0, Tutor LMS 4.1.2 and Tutor LMS Pro 4.1.1 (not 4.0.4). So Tutor LMS Pro is already at the version bundled with the current theme, and the two plugins are in sync.

Two notes:

1. Tutor LMS 4.1.3 (the free plugin) was released today with a security fix. Please update it from Dashboard > Updates.

2. The “A valid license key is required to update Tutor LMS Pro” message comes from the Tutor LMS Pro plugin itself: the “update now” link on the Plugins page works only with a Tutor LMS Pro license key activated under Tutor LMS > Settings > License. You don’t need that link with Efor. Tutor LMS Pro is updated together with the theme: when a new Efor version ships a newer Tutor LMS Pro, go to Appearance > Install Theme Plugins and update it from there; that page does not ask for a license key. Tutor LMS Pro 4.1.2 (released on 12 October) will be included in the next Efor update.

If the license key we issued for your domain shows as inactive or invalid on the License page, let us know in this topic with your final URL and we will check it:
https://www.pixelwars.org/forums/topic/tutorlms-pro/

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thank you for the access details. Unfortunately the login does not work: WordPress rejects the username/password combination you posted. Could you please check them, or create a new temporary administrator account for us (Users > Add New, role Administrator) and post the details in the Private Content field again? We will delete it when we are done.

What we found in the meantime:

1. We tested Interioz with Elementor 4.3.5 on our own installation: the page CSS and the global (kit) CSS are generated and loaded correctly. So the theme does not block Elementor’s CSS.

2. On your site the problem is site-wide: on the homepage, About Us and the blog posts, Elementor does not load its page CSS file and its global kit CSS at all, even though the files exist on the server. This happens on every page, which means Elementor’s CSS generation itself is failing on your site, most likely because of a PHP error or a plugin conflict inside Elementor’s element registration. The site still looks partly rendered because Elementor serves the cached HTML of the pages.

While we wait for working access, two things you can do:

– Elementor > Tools > General > Safe Mode: enable it and open the Elementor editor on a page. Safe Mode disables all other plugins and the theme for the editor only. If the editor works in Safe Mode, a plugin is causing it; the usual suspects are the Elementor add-ons.

– Ask Hostinger support for the PHP error log of the last two days (or enable WP_DEBUG_LOG and send us wp-content/debug.log). The error that breaks Elementor’s CSS generation should be in there.

Please do not restore the backup again for now; it hides the error without fixing it.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

We understand this is urgent, so here is what we found after checking the site again today and comparing it with yesterday.

1. The theme is not involved. Interioz and our core plugin contain no code that touches Elementor’s generated CSS files or the uploads folder, and the theme’s own CSS loaded correctly on both days. The files that fail are the ones Elementor generates in wp-content/uploads/elementor/css/, and that happens independently of the theme. Elementor 4.3.5 is fine to use with the theme.

2. The site is still partly unstyled right now, even on the restored backup. The page CSS file (post-16958.css, 146 KB, with all heading styles) and the kit CSS file (post-7.css) exist on the server, but Elementor does not link them in the page, so headings and typography fall back to defaults. Yesterday it was the opposite: Elementor linked files that the server could not find. In both cases, what Elementor has stored in the database does not match the files on disk. That is the signature of a stale cache layer, most likely a persistent object cache (Redis/Memcached, usually enabled in LiteSpeed Cache > Cache > Object on Hostinger) that was not flushed when the backup was restored, on top of the page cache and the CDN cache.

3. Correction to our previous reply: “Internal Embedding” only covers part of the styles; the new container styles are always written to files. Please leave CSS Print Method on “External File”.

Please do these steps in this order:

a) LiteSpeed Cache > Cache > Object: turn Object Cache OFF for now (you can turn it back on once the site is stable). Then LiteSpeed Cache > Toolbox > Purge All.

b) Elementor > Tools > General > “Clear Files & Data”.

c) Open the homepage in a private window; all pages should be styled again.

d) Purge the CDN cache in Hostinger hPanel.

e) Update Elementor to 4.3.5 again, then repeat a) to d).

If the site breaks again a few hours later, please note the exact time and ask Hostinger whether a scheduled task (cache clearing, file sync, cron) runs at that time, and ask them to confirm that wp-content/uploads/elementor/css/ is writable and readable by the web server.

If you prefer, add a temporary admin login in the Private Content field and we will check Elementor’s System Info and the cache settings directly.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

We checked your site. All theme files load correctly; the problem is in the CSS files that Elementor generates for your pages.

Elementor writes the styles of every page into files under wp-content/uploads/elementor/css/ (for the homepage: base-desktop.css and local-16958-frontend-desktop.css). WordPress still links these files, which means Elementor believes they exist, but the web server returns a 404 for them. So the files are either being written to a different folder than the public uploads folder, or the server cannot read them. Without them, all layouts, backgrounds and typography built with Elementor are lost, on every page.

Quick fix (takes a minute):

1. Go to Elementor > Settings > Performance, set “CSS Print Method” to “Internal Embedding” and save. Elementor then prints the styles inside the page and no longer depends on those files.

2. Purge the caches: LiteSpeed Cache > Purge All, and the CDN cache in Hostinger hPanel.

3. Open the site in a private/incognito window.

To find the actual cause, please ask Hostinger support to check two things: that WordPress’s upload path points to the public wp-content/uploads folder (Settings > Media, or an UPLOADS constant in wp-config.php), and that wp-content/uploads/elementor/css/ and the files in it are readable by the web server. Once that is fixed you can switch CSS Print Method back to “External File” and run Elementor > Tools > General > “Clear Files & Data”.

Did this start right after Elementor was updated to 4.3.5 (released October 13)? If yes, please tell us; as a test you can reinstall the previous version from Elementor > Tools > Version Control.

One more note: the About Us and Commercial Interior Design pages have the same icon problem we fixed on the homepage (about 10 MB and 8 MB of HTML). Replacing those icons the same way will speed up those pages too.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Tomas,

Since the scrolling issue was resolved by deactivating the third-party plugins and there has been no further activity for over 30 days, we’re closing this topic to new replies.

If you haven’t already, you can reactivate your plugins one at a time, checking the scrolling after each one, to find the plugin causing the conflict. Since we no longer need access to your site, we’d also recommend changing your admin password and re-enabling your GeoIP filter.

If you need any further help, please open a new topic and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi @stev,

Thanks for your purchase!

The line is purely decorative, so the theme works exactly the same without it. You can control it in Appearance > Customize > Header > General > Header Transparent Style:

– Minimal: no line
– Border Bottom: full-width line (as in Demo 13)
– Border Bottom Fixed: the line is limited to the width of the logo and menu area
– Border All: a thin border around the whole header

Select “Minimal” to remove it. The line is always at the bottom edge of the header, and it only appears when the header is transparent (floating over the top image); the sticky header doesn’t show it.

If you want to keep the line but change its color, add this to Appearance > Customize > Additional CSS and adjust the color value:

.is-header-transparent-border-bottom .site-header:not(.clone) .header-wrap {
	border-bottom-color: rgba(255, 255, 255, 0.5) !important;
}

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Since there has been no further activity on this topic for over 30 days, we’re closing it to new replies.

If the portfolio page is still showing the blog layout after setting its Template to “Portfolio” in the page settings on the right, please open a new topic with a link to the page and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi @nazli,

Good news: we added this feature to Lahanna. It is available in Lahanna 4.3.0, released today.

1. Update the theme:

– Download the latest version from https://themeforest.net/downloads (“Installable WordPress file only”).

– Go to Appearance > Themes > Add New > Upload Theme, upload lahanna.zip and choose “Replace active with uploaded”.

– Keep your child theme (Lahanna Child Style 4) active; you do not need to change it.

Details: https://docs.pixelwars.org/lahanna.php#update-theme

2. Update the Pixelwars Core plugin:

– After the theme update, go to Appearance > Install Theme Plugins and update “Pixelwars Core” to version 7.0.0.

Details: https://docs.pixelwars.org/lahanna.php#update-theme-plugins

3. Add an image to a category:

– Go to Posts > Categories and click a category to edit it.

– In the “Header Image” field, click “Select Image”, choose an image and click “Update”.

– Open the category page: the image is shown at the top as a full width header, with the category title (and the category description, if you added one) centered on it. The post list stays below as usual.

Details: https://docs.pixelwars.org/lahanna.php#post-categories

You can choose a different image for each category. The image also appears in a “Header Image” column in the categories list. Categories without an image keep the current plain title.

Tip: use a wide (landscape) image, at least 1920px wide, so it looks sharp on large screens.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Jo,

Since the transparent header issue has been resolved and there has been no further activity on this topic for over 30 days, we’re closing it to new replies.

If you need any further help, please feel free to open a new topic and include a link to this one so we can pick up where we left off.

Thanks again for your patience.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Since all the questions in this topic have been answered and there has been no further activity for over 30 days, we’re closing it to new replies.

If you need any further help with the homepage slideshow (either the theme’s “Homepage Bg Slide Speed Up” template or your custom Elementor Canvas page), please open a new topic and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi,

Since both questions in this topic have been answered and there has been no further activity for over 30 days, we’re closing it to new replies.

If you’d still like help with the floating buttons (for example, if you don’t have Elementor Pro and would prefer the code snippet), please open a new topic and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi,

Since there has been no further activity on this topic for over 30 days, we’re closing it to new replies.

If you’d still like help with the checkout button or site speed, please open a new topic with the details mentioned above (payment gateway, caching plugin, the CSS you added, and a PageSpeed or GTmetrix result) and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi,

Since this issue has been resolved and there has been no further activity for over 30 days, we’re closing this topic to new replies.

If you need any further help, please feel free to open a new topic and include a link to this one so we can pick up where we left off.

Thanks,
Pixelwars Support

[Mehmet S.]

Hi Roger,

Great news, thanks for the update. I re-checked your site from the outside and can confirm the fix:

– 8 and 16 parallel requests now all succeed; yesterday 6 out of 8 returned 503.

– PHP is now 8.5.11. Energi 1.0.2 is PHP 8.5 compatible and I see no PHP warnings in your pages.

– Your pages are also much lighter now: the home page went from 812 KB / 14 s to 194 KB / 2.3 s, and the About page from 411 KB / 8.5 s to 139 KB / 1.9 s. The CSS print method and the Essential Addons inline CSS changes clearly worked.

Why the editor still feels slow: the server no longer rejects requests, but it still processes PHP requests almost one at a time. A single page takes about 2 s, but when 8 requests arrive together each one takes about 14 s. The Elementor editor sends dozens of requests when it opens, so it waits on the server. This is CPU / PHP worker capacity of the hosting plan, not the theme.

What will help most:

1. Ask GoDaddy to confirm OPcache is enabled for PHP 8.5 (WordPress Site Health reported it as disabled) and to tell you how many PHP workers / CPU cores your plan allows. If the editor is still slow after that, a plan with more CPU or a different host is the real fix. Our hosting recommendation is in the requirements topic:

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

2. Install a page cache plugin (for example WP Super Cache or LiteSpeed Cache). Your pages are still generated by PHP on every visit (no cache headers), which keeps the server busy and slows the editor for you too.

3. Keep reducing active plugins. Each plugin runs on every one of the editor’s requests.

4. Turn off WP_DEBUG in wp-config.php if it is still on.

If you want, I can take another look inside the admin once the cache plugin is in place.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Roger,

Thanks for giving us access. I reproduced the problem on your site and found the cause. It is not the theme or Elementor itself; your server is rejecting requests under load.

What happens:

– When the Elementor editor opens, it sends many requests to the server at the same time.

– Your server answers some of them with “503 Service Unavailable” (a 23-byte Apache error, not generated by WordPress).

– The editor preview frame (yoursite.com/test1/?elementor-preview=13486) was one of the requests that received a 503, so the editor stays on the “Loading” screen forever. The browser console shows the matching error: “Blocked a frame … from accessing a cross-origin frame”.

How I confirmed it:

– 8 parallel requests to /about/: 2 succeeded, 6 returned 503.

– 8 parallel REST API requests: 3 succeeded, 5 returned 503.

– 8 parallel requests to a static CSS file: all succeeded in ~250 ms. So the limit is only on PHP processes, not on the network.

– A single page request succeeds but takes 8 to 14 seconds to generate.

– Even the WordPress Site Health page returns 503 when opened while the editor is loading.

Your hosting is CloudLinux based (cPanel / LVE). This pattern (503 as soon as several PHP requests run at once, static files fine) is the Entry Processes / PHP-FPM worker limit of the hosting account being reached. Please send GoDaddy this information and ask them to:

1. Check the account’s LVE / Resource Usage report (cPanel > Resource Usage) for “Entry Processes” and CPU/IO limit faults during the time you tried to open the editor.

2. Raise the Entry Processes / PHP-FPM max children limit, or move you to a plan that allows more concurrent PHP processes.

3. Enable OPcache for PHP (Site Health reports it is disabled).

Things you can do on your side to make each request much lighter, which will reduce the 503s:

1. Elementor > Settings > Performance > CSS Print Method: set to “External File” (currently “Internal Embedding”, which adds ~117 KB of CSS to every page).

2. Essential Addons is printing all of its CSS inline: 500 KB on the home page and 1.1 MB in the editor preview. In Essential Addons > Tools, regenerate assets and make sure the inline/”Generate assets in the uploads folder” option is set to file mode, or disable the Essential Addons elements you do not use.

3. Reduce active plugins (currently 29). Remove duplicates (Loginizer + Loginizer Pro, FormLayer + FormLayer Pro, Filter Everything + Filter Everything Pro keep only the Pro one), and deactivate setup/import tools you no longer need (One Click Demo Import, WordPress Importer, Extendify, Site Assistant, Search & Replace Everything, Envato Market).

4. Install a page cache plugin (for example LiteSpeed Cache or WP Super Cache) so visitors do not trigger PHP on every page load.

5. Turn off debug mode: in wp-config.php set WP_DEBUG to false (Site Health also flags that errors are displayed to visitors).

Our server requirements are listed here:

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

Your PHP version and memory values already meet them, so the remaining issue is the concurrent process limit, which only the host can change.

Let us know what GoDaddy says and we will be happy to look again.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @reetsingh,

That error comes from Amelia’s “Activate with Envato” button, not from Efor. That button checks whether your Envato account has purchased Amelia itself. Amelia is bundled with Efor, so your Efor purchase can’t activate it there, and retrying won’t change the result.

The Amelia version bundled with Efor works fully without activation; activation is only needed for Amelia’s own automatic updates. Bundled plugin updates come with Efor updates: update Efor, then go to Appearance > Install Theme Plugins and update Amelia from there.

If you’d like to activate Amelia anyway, please request a license key for your final domain in this topic:

https://www.pixelwars.org/forums/topic/tutorlms-pro/

Then enter the key in the “Purchase code” field under Amelia > Settings > Activation (not the “Activate with Envato” button).

Could you also let us know your Efor and Amelia versions (from the Plugins page)? If you still need help, please share your wp-admin login details via the Private Content box and we’ll take a look.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @nazli,

1. Blog
Please keep “Your homepage displays” set to “Your latest posts”. In this theme, the slider, the image categories and the post list belong to the posts page. If you switch to “A static page”, they would move to the new Blog page and your homepage would lose its current design.

The right way is the one you have already set up: the “Bloq” category with a “Bloq” link in the menu. I checked https://lezzetlimetbex.com/category/bloq/ and it works correctly. Just assign your blog posts to this category.

Note: posts in the “Bloq” category also appear in the post list on the homepage, because the homepage shows all latest posts.

2. Slider
I checked the slider on desktop and mobile. All 5 slides and their images load, and there is no error on the page. You may be referring to one of these:

– The slider shows the demo posts. The Main Slider widget (Appearance > Widgets > Blog Featured Area) is set to show “Sticky posts”, and the 5 sticky posts are demo posts. To show your own posts, mark them as sticky (Posts > Quick Edit > “Make this post sticky”) and un-stick the demo posts. Or set “Slides” to “Latest posts” in the widget.

– “Uncategorized” above the slide title is the post’s category. Assign the post to another category to change it.

– On mobile, the slider is 450px tall because of the “height: 450px” rules in your Additional CSS.

If it is something else, please upload a screenshot to Google Drive (or any image sharing site) and paste the link here.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for the update. Removing the icons worked: your homepage HTML is now about 250 KB instead of 5.3 MB.

We checked the page again. The remaining delay comes from the number of files the page loads: about 100 separate files (51 CSS and 50 JavaScript files, around 2 MB in total). The browser cannot draw the page until all CSS files are downloaded. Also, with the logo-centered header layout, the menu is shown only after the page scripts have finished loading, so the header appears a bit later than the rest of the page. Fewer files will shorten both delays.

Please try these steps:

1. LiteSpeed Cache > Page Optimization > CSS Settings: turn on “CSS Combine” (CSS Minify is already on).

2. LiteSpeed Cache > Page Optimization > JS Settings: turn on “JS Combine”. If anything on the page stops working after this, turn it off again. Please do not set “Load JS Deferred” to “Delayed”. With that option, the header would stay hidden until the visitor moves the mouse or scrolls.

3. The Popup Box plugin loads on every page, but its only popup is the demo one (“Demo Title”). If you don’t use it, please deactivate the plugin.

4. Save, then purge the cache: LiteSpeed Cache > Purge All, and also the CDN cache in Hostinger hPanel.

Also, the sections that fade in while you scroll down use Elementor entrance animations. This is an effect, not slowness. If you want them to appear immediately, edit the widget and go to Advanced > Motion Effects > Entrance Animation: None.

Let us know how it goes.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Zenz,

Great to hear it’s working now, and thanks for letting us know!
I’ll close this topic now. If you need anything else, feel free to open a new one.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Zenz,

Thank you for your patience. We’ve found the cause of the washed-out dashboard.

Your child theme contains copies of Tutor LMS template files in this folder:

wp-content/themes/efor-child/tutor/

These files come from an older version of Tutor LMS (3.x), and they override Tutor LMS’s own templates. Tutor LMS 4 completely redesigned the dashboard, and its stylesheet no longer includes styles for the old layout, so the dashboard looks unstyled. Updating Efor didn’t help because files in the child theme always take priority.

To fix it:

1. Connect to your site via FTP or your hosting file manager.

2. Download a backup copy of the wp-content/themes/efor-child/tutor/ folder.

3. Rename the folder to “tutor-old”.

4. Clear your cache (caching plugin, server cache, CDN) and reload the dashboard.

Tutor LMS will then use its own up-to-date templates, and the dashboard should display correctly.

If you made custom changes in any of those files, please redo them on top of the new Tutor LMS 4 templates (wp-content/plugins/tutor/templates/), copying only the files you actually need to change.

The temporary login link you shared has expired, so we couldn’t check this from inside your site. If the issue persists after renaming the folder, please send us a new login link and we’ll take a look.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thank you for the link. We checked your homepage and found what is slowing it down.

Your server and cache are working fine: the server responds in about 0.3 seconds. The problem is the size of the page itself. The homepage HTML is about 5.3 MB, while a typical page is around 150-200 KB.

Almost all of this comes from the 4 icons in the Icon Box widgets (Partners, Sample Flats, Pricing, Team). These icons were uploaded as SVG files, but they are not real vector icons: each SVG contains a large 1536×1024 px PNG image, about 1.3 MB each. Elementor places uploaded SVG icons directly into the page code, so every visitor has to download these 4 images as part of the page before it can finish loading. A cache plugin cannot help here, because it only serves the same heavy page faster.

In our test, a first visit took about 11 seconds before the page was ready. Repeat visits are fast because the browser has already cached the page, so the site may look fine on your own computer.

How to fix it:

1. Edit the homepage with Elementor.

2. In each of the 4 Icon Box widgets, replace the uploaded SVG with one of these:
– an icon from the Icon Library (click the icon and choose “Icon Library”),
– a real vector SVG icon (usually just a few KB),
– or an Image Box widget with a small image (for example 150×150 px, WebP or PNG).

3. Click Update, then purge the cache: LiteSpeed Cache > Purge All, and also the CDN cache in Hostinger hPanel if it is enabled.

After this, the homepage HTML should drop from about 5.3 MB to under 200 KB, and the page should load much faster.

Let us know how it goes.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thank you for reporting this and for providing the screenshots.

I’ll take a closer look at the dashboard styling issue with “Tutor LMS 4” and the latest version of the Efor theme to determine what is causing the washed-out appearance.

I’ll investigate the issue and get back to you with an update as soon as I have more information.

Thanks for your patience.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @nazli,

I updated the Lahanna theme and the Pixelwars Core plugin on your site to the latest versions.

With this update, the “Page Header Style” option is available again in the page/post editor, so the Demo-04 header style (Half Transparent over the featured image) now shows on the pages and posts where the demo set it.

I also made two small adjustments so everything displays correctly:
– In “Customize > Additional CSS”, your fixed header rule now applies only to the homepage (“.home .site-header …”). On inner pages it was covering the page titles.
– On the “About Me” page, I set “Page Header Style” to “Inherit from Customizer”, because its page style (Classic Full) shows the title above the image.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @nazli,

I logged into your site and fixed the issues:

1. Customizer changes not appearing on the live site
The main button in your Customizer was set to “Save Draft”, so your changes were saved as a draft and never published. I published your saved changes and switched the button back to “Publish”. From now on, your changes will go live when you click “Publish”.

2. Logo settings
“Logo Padding (px)” was set to 54. This added 108px of empty space on each side of the logo, so the logo was squeezed and the height options had no visible effect. I set it to 0, so the height options work now.
I also set “Image Logo Height” to 40px and “Image Logo Height Mobile” to 44px so the logo fits inside your header. If you want a bigger logo, first increase “Customize > Header > Menu > Menu Height (px)”, then increase the logo height.
Note: “Logo Margin” is not used in the “Header Small” layout.

3. “About Me” page
Your Page Style setting (“Classic Full”) is now published and applied to the page.

4. Additional CSS
I removed an extra “}” in your custom CSS that was breaking the rule after it.
Your custom CSS also makes the header fixed on all pages, so on inner pages it slightly covers the page title. If you only need it on the homepage (for the slider), start those selectors with “.home ” (e.g. “.home .site-header { … }”).

5. Moving vertical line
I could not find it on the front-end. Could you please send a screenshot or a short screen recording, and tell us which screen it appears on?

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Tom,

You’re welcome! Good luck with the build, and feel free to open a new topic if anything else comes up.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for your patience, and I’m sorry this turned into such a stressful process.

What you’re seeing is how WP Delicious is built: every recipe is its own post under /recipe/, and its importer (Free and Pro) creates new recipe posts instead of converting the cards inside your existing posts. There’s no in-place option, so re-running it won’t change the result.

Fuud’s recipe features come from WP Delicious, but you can use Fuud without it: regular posts work as a normal blog, and Tasty Recipes renders its own card inside the post content. For a site with 2,000+ ranking posts, I’d recommend keeping your posts and Tasty Recipes as they are and skipping the migration.

For the cleanup: WP Delicious saves imported recipes as drafts, so unless you published them, they were never public. You can confirm by opening one of the /recipe/ URLs in a private browser window.

1. Take a full backup.

2. Check that your recipes are still under WP Tasty > Tasty Recipes. If the importer’s option to delete the originals was used, stop here and restore them from a backup taken before the import.

3. Go to Recipes > All Recipes (reactivate WP Delicious first if it’s off), move them all to Trash, then empty the Trash. Raising the items per page in Screen Options speeds this up.

4. Deactivate and delete WP Delicious and WP Delicious Pro.

This only removes the imported copies; your original posts aren’t affected.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thank you for the detailed information.

I will investigate this issue today and check how the Tasty Recipes to WP Delicious migration works with the Fuud theme, especially regarding the duplicate /recipe/ URLs and the original post structure.

I will get back to you with my findings.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Tom,

The demo content is now in place. Elementor’s “Container” feature was turned off on your site, and since the Arkiz demos are built with containers, Elementor was skipping most of each layout. I’ve turned it on, so please keep it active.

Some fonts, colors and content widths may still look slightly different from the demo. These come from the global styles in your Elementor Site Settings, not from the theme.

You can delete the temporary login now. If you’re happy with the theme, a rating on ThemeForest would be much appreciated: https://themeforest.net/downloads

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Sorry for the late reply.

The Portfolio page in the demo uses the “Portfolio” page template, which automatically displays your portfolio posts. It’s a static template with no content area, so it can’t be edited with Elementor. That’s why you’re seeing this message. Clearing Elementor’s cache or changing its settings won’t affect this.

To change what appears on the page, add or edit your portfolio posts; they’re listed there automatically. The portfolio posts themselves can be edited with Elementor as usual.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Tom,

Thanks for updating the server settings. The login link you sent has expired, so I can’t access the dashboard.

Could you please create a new one? I’ll import the demo content as soon as I have access.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi Tom,

I checked your site. The server’s PHP limits are below the theme’s requirements, which is why the demo layouts aren’t importing completely.

Please ask your host to raise them to the values listed here:

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

Once that’s done, let me know and I’ll re-import the demo content for you. I’ll need to replace the incomplete demo pages, so tell me if there’s anything on them you want to keep.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @nazli,

I checked your website and found the cause of the issue.

Under “Appearance > Widgets”, there were two “Main Slider” widgets added to the “Blog Featured Area” widget section. Having two Main Slider widgets in the same area caused a conflict and broke the layout on the site.

I removed the second “Main Slider” widget, and the issue is now resolved.

Please check your website again and let me know if everything looks correct on your side now.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello @tarkansert,

Tutor LMS Pro is now activated on your site. Please change the admin password you shared with us now that it’s done.

One more thing I noticed while I was there: your server settings are below our recommended values. The theme works with the premium plugins much better when they are met, so I’d suggest asking your hosting provider to apply them:

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

You can check your current values under:

–> WP Admin > Tools > Site Health > Info > Server.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi @nazli,

I logged into your site and checked the Customizer. It is loading and working correctly on my end. Please try again on your side.

I also see that you imported “Demo-04”. To get the complete design of that demo, the matching child theme needs to be installed:

1. Go to https://themeforest.net/downloads and download the full package: “All files & documentation”.

2. Inside the package, the “Parent Theme” folder contains the main theme. This is already installed on your site.

3. Open the “Child Themes” folder and install “lahanna-child-style-4” (Appearance > Themes > Add New > Upload Theme).

4. Activate the child theme.

Once the child theme is active, the full “Demo-04” styling will be applied.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello @tarkansert,

I’ve sent your Tutor LMS Pro license key to your registered email address. Please check your spam folder too.

If it doesn’t connect, share your WordPress admin login details in the “Private Content” box below and I’ll activate it for you.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for sending the login details. Unfortunately, I can’t reach your site at all — the URL doesn’t load on my end, so I’m not able to log in and check the import.

Could you please confirm that the URL is correct and that the site is publicly accessible? If you have a security plugin, a server-side firewall, or a maintenance/coming-soon mode active, it may be blocking my access. Whitelisting my access or temporarily disabling it should solve it.

Once I can get in, I’ll look into the demo import error right away.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello @rob,

Tutor LMS Pro is activated on your site. Please change the admin password you shared with us now that it’s done.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello,

Prime Slider is temporarily closed on the WordPress.org repository, which is why the theme’s plugin installer couldn’t download it. I’ve installed it from the author’s official site and activated it on your install, along with the Core Widgets the theme’s slider sections need.

Please read this before updating the plugin later. It covers where to download it from and why:

https://www.pixelwars.org/forums/topic/prime-slider-installation-update-and-security-notice/

Also worth changing your admin password now that I’m done, since it was shared over the forum.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for the clear report and for sharing your URL — that made this easy to check.

The good news is this isn’t a Portfolio or theme issue. Pretty permalinks aren’t currently active anywhere on your site. Every link WordPress generates is still in query format:

Blog posts → ?p=645
Pages → ?page_id=759
Categories → ?cat=15
Pagination → ?paged=2

WordPress generates these links from the permalink setting in the database, independently of the theme and of your .htaccess. If the structure were actually set to Post name, those links would read /post-title/ even if rewriting were broken. Since they don’t, the structure is still on “Plain” — which is exactly why /portfolio/a-une-passante/ returns 404 while ?portfolio=a-une-passante works. Portfolio just happens to be where you noticed it first.

To fix it:

1. Go to “Settings → Permalinks”, select “Post name”, and click “Save Changes”.

2. Reload your homepage and hover a blog post title. If it now reads /personne-ne-changera-davis.../, the setting saved correctly.

3. If it still reads ?p=645, the setting is being reverted. Temporarily deactivate caching, security and SEO plugins and try again.

4. If it saves but URLs then return 404, ask your host to confirm that mod_rewrite is enabled and .htaccess is writable (or, on nginx, that the WordPress rewrite block is present).

Once that’s sorted, please clear any page cache and check a Portfolio item again. If it still 404s at that point, reply here and I’ll look further.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello,

Good news. The plugin author has published a fixed free version of Prime Slider on their own site, so you can install it without waiting for the WordPress.org repository to reopen.

Here are the steps:

1. Go to https://primeslider.pro/pricing/ and click the “Free Download” button at the bottom of the Free column. This is the plugin author’s own official site rather than a third-party mirror, and I downloaded and reviewed the file myself before recommending it here.

2. In your WordPress admin, go to Plugins > Add New > Upload Plugin, select the ZIP you downloaded, then install and activate it.

3. Open the “Prime Slider” menu in your admin sidebar and go to the “Core Widgets” page. Click “Activate All”, then click “Save Settings”. Not all widgets are enabled by default, and the demo content won’t render correctly without this step.

4. Run the demo import.

If you have already run the demo import, there’s no need to repeat it. Complete steps 1 to 3 and the slider sections will render on their own.

The plugin is still closed on WordPress.org while its review is completed. I’ll post here when it’s restored so you can switch back to normal automatic updates.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello,

I understand the disappointment. The slider sections are a big part of how the demo looks, and I’d want them working too.

To be clear about what’s happening: The theme itself is fully functional and the demo import will complete normally. The slider sections are built with Prime Slider, a free third-party plugin that was temporarily closed on the WordPress plugin repository on August 7, 2026, pending a security review of its author’s infrastructure. That closure is on WordPress.org’s side, so it isn’t something I can work around by sending you a copy. Installing one from an unofficial download site while a security review is open would put your site at risk.

I’ll post here the moment the plugin is restored. Once you install it from the official repository, the imported slider sections will render exactly as they do on the demo, with no re-import or rebuild needed.

If you’d rather not wait at all, you can submit a refund request at themeforest.net/refund_requests/new.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hello,

Thank you for reporting this issue and for providing the details.

I’ll investigate the “Prime Slider” plugin issue and the “Secury” demo import process today. I’ll check the best solution for importing the demo content and get back to you with an update as soon as possible.

Thank you for your patience.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thank you for reporting this issue.

I’ll investigate the Portfolio Standard permalink/404 issue today and get back to you with an update.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

The Projects page uses a static portfolio page template, so it cannot be edited with Elementor. It simply lists the portfolio posts you create under the Portfolio section in the WordPress admin menu.

The Products page, on the other hand, is a standard page built with Elementor, so you can freely edit its content there.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

I had a look at your home page. Before I give you a fix, could you send a screenshot showing how it currently looks on your screen, and let me know whether you’re seeing this on desktop, tablet or mobile?

The thumbnail size in that section is set inside the Elementor widget, so knowing exactly what you’re seeing will let me point you to the right setting straight away.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for reaching out. I’ll take a look at your site today and get back to you with a fix.

Best regards,
Mehmet
Pixelwars Support

[Mehmet S.]

Hi,

Thanks for waiting. Nothing is missing from your package. “Demo 1” contains every homepage and portfolio layout available in ArtFlow. The layouts aren’t separate demos; they’re page templates you select per page.

To switch to “Portfolio Grid”:

1. Go to “Pages” and open the page you’re currently using as your homepage (or create a new page).

2. In the editor sidebar, open the “Template” dropdown.

3. Select the “Portfolio Grid” template.

4. If you also want to drop the dark styling, open “Page Settings” in the sidebar and disable “Dark Mode”.

5. Update the page. (If you created a new page instead, set it under Settings > Reading > Your homepage displays.)

More details in the docs:
https://themes.pixelwars.org/doc/artflow/

Best regards,
Pixelwars Support