Hello, Thank you for your message.

Can you please provide what is the source of this information?

Is the affected file provided?

Konzept v2.5 has rather short and simple PHP that is not accepting user input in almost any place, so this may be invalid.

The two errors were first revealed to me a few days ago through an automated scan from my iThemes Security Pro plugin. I don’t want to post the full link to the report here for security reasons, as Konzept is still running on the site (Version 2.5).

So then I looked for Konzept on the iThemes weekly security blog (which is an amazing resource by the way) and sure enough, I found an older post from 2020 that reported a separate incident with the Konzept theme for versions below 2.5: https://ithemes.com/blog/wordpress-vulnerability-roundup-august-2020-part-2/#ib-toc-anchor-24

The iThemes blog also pointed me in the direction of these sites describing the exploits. https://jannefi.blogspot.com/2012/09/xss-vulnerability-in-multiple-premium.html https://vladvector.ru/exploit/2020-07-30-konzept-fullscreen-portfolio-wordpress-theme-v2-3.txt https://en.0day.today/exploits/22667

Thank you.

But in the first link it says that it’s “fixed” and the link to the original vulnerability description doesn’t work.

It seems they mention the issue, which we once had, which was this:

1. In wp-head.php we were printing the entry’s title (page’s or post’s) without applying wp_title filter, which is described here: https://developer.wordpress.org/reference/functions/wp_title/

2. To exploit this issue some not trusted third party would have to have access to the Administration panel. So, it wasn’t affecting many people.

3. This also wasn’t filtering the search query, so anyone could execute JavaScript on the front-end. Typically this shouldn’t have any negative consequences since accessing authentication cookies wouldn’t be possible anyway but how it could be used depends on the source code of the remaining components, so it’s unknown.

This issue has been fixed around 2013-2015.

Nevermind, we solved the issue with our hosting, it seems that the shortcode block tends to trigger a false positive on the sever firewall.

Hello, indeed it sounds like something related to WordPress. In the theme we only register blocks using WordPress’s API so all content modification and saving is handled by WordPress.

I found the 3.1 in the repository, but the project gallery is still absent

Hello, since we updated to Gutenberg (2 years ago) the previous SuperSlide editor is no longer available.

We recommend that you import one of the sample projects in Ikon Importer and check how it’s set up.

The projects should be backwards compatible.

Thanks for the reply! I see… one Classic Editor is deactivated, I can look at the shortcode structure. Have a nice week end. Kind regards.

Thank you for your reply and for your availability to help us. Yes, in your demo it scales perfectly.

This is the URL to the Konzept 2.5 Featured Slideshow that doesn’t scale (the one we are using now, on WordPress 5.9)

https://www.riccardomagherini.com/fineart/

This is to the Konzept 2.2 Featured Slideshow that does scale (the old one, that we are not using, on WordPress 4.8)

https://www.riccardomagherini.com/fineart-old/

Could be something in the customized child style.css coming from the previous version?

this is the content:

/* Theme Name: Child Konzept 2.5 Theme URI: Description: Child theme of konzept theme for the Konzept theme Author: Ikonize Author URI: Template: konzept Version: 2.5 /

/ Generated by Orbisius Child Theme Creator (https://orbisius.com/products/wordpress-plugins/orbisius-child-theme-creator/) on Thu, 17 Feb 2022 10:15:13 +0000 / / The plugin now uses the recommended approach for loading the css files./

@import url(’../konzept/style.css’);

.selector { font-family: Roboto, sans-serif; font-weight: 100; }

.wp-caption .wp-caption-text, .entry-caption, .gallery-caption { font-size: 87.5%; / line-height: 1.25; / font-style: normal; }

p { margin: 0 0 3em 0; font-size: 106.25%; line-height: 1.625; font-weight: 300; }

/ Project Title and Description /

.project-title { margin-left: 10% } .project-description { margin-left: 10% } .project-description:empty { margin-bottom: 3em; }

/ Project View /

.project-slide-image { margin: 0 auto; cursor: -webkit-grab; background-color: #191718; }

.project-slide .description h6 { color: #ffffff; opacity: 0.5; font-size: 18px; font-family: Novecentowide, sans-serif; text-transform: uppercase; clear: both; margin-bottom: 10px; }

.portfolio-arrow-left, .portfolio-arrow-right { opacity: 0.3; } .portfolio-arrow-left:hover, .portfolio-arrow-right:hover { opacity: 1; }

.white .sharing-icons a { color: #E3E3E3;; } .sharing-icons a {color: #444444; opacity: 0.6; }

/ Close Button /

.portfolio-cancelclose { opacity: 0.6; }

.page-template-content a { color: #222222; font-weight: 100; text-decoration: underline; }

/* link style in blog /

body { color: #505050; line-height: 1.625; margin: 0; opacity: 0; height: 100%; } .body-visible { opacity: 1; -webkit-transition: opacity 700ms; transition: opacity 700ms; } .has-featured-slideshow { overflow-y: hidden; }

a { color: #444444; text-decoration: none; } a:visited { } a:focus { outline: thin dotted; } a:active, a:hover { color: #222222; outline: 0; } a:hover { text-decoration: underline; } a img { border: none; }

/* * 4.1 Site Header * —-—-—-—-—-—-—-—-—-—-—-—-—-—-—— /

.site-title { color: #969696; } .site-title:hover { color: #444444; } .site-description { font-family: Roboto, sans-serif; color: #969696; font-size: 13px; text-decoration: none; margin: 2px; }

/* * 4.3 Navigation * —-—-—-—-—-—-—-—-—-—-—-—-—-—-—— /

.pf_nav li a { display: inline-block; color: #969696; font: 700 68.75%/1 Novecentowide, sans-serif; } .pf_nav li a.selected { color: #969696; } .pf_nav li a:hover { color: #444444; text-decoration: none; }

.nav-menu li a { display: inline-block; color: #969696; font: 700 68.75%/1 Novecentowide, sans-serif; text-decoration: none; } .nav-menu li a:hover { color: #666666; }

.nav-menu > .has-submenu > a:hover { color: #666666; }

.nav-menu li li a:hover { background-color: #bdbdbd; color: #666666; font-weight: 700; }

.nav-menu .children { background-color: #000; background-color: rgba(0, 0, 0, 0.9); border-radius: 4px; color: #BABABA; display: none; float: left; left: 100%; top: 0; font-weight: 500; padding: 0; position: absolute; word-wrap: break-word; z-index: 9999; }

.nav-menu ul ul a { color: #BABABA; margin: 0; min-width: 180px; }

.nav-menu ul ul a:hover { background-color: #bdbdbd; color: #666666; font-weight: 700; }

.nav-menu > .current-menu-item > a { color: #666666; }

.nav-menu li .current-menu-item > a { background-color: #bdbdbd; color: #666666; font-weight: 700; }

/* * 5.1 Entry Header * —-—-—-—-—-—-—-—-—-—-—-—-—-—-—— /

.page-title { word-wrap: break-word; font: 900 968.75%/0.8125 Novecentowide, sans-serif; color: #000; border-bottom: 2px solid #D9DCDD; max-width: 1200px; margin: 0 auto; text-transform: uppercase; width: 92%; padding-bottom: 16px; clear: both; text-align: center; letter-spacing: -2px; margin-top: -0.375em; }

/* * 5.14 Recent Blog Posts and Recent Portfolio Entries * —-—-—-—-—-—-—-—-—-—-—-—-—-—-—— / / Related Posts */

.related-posts { padding: 35px 0 40px 0; background-color: #ffffff; }

.related-posts-title a { color: #000; font: 900 150%/1 Novecentowide, sans-serif; float: left; margin-bottom: 0.25em; } .related-posts-title a:hover { color: #888888; text-decoration: none; }

Yes, the CSS is definitely modified and is the most likely cause.

As a quick fix you can add this to CSS (at the bottom):

.slide-img { width: 100%; height: 100%; object-fit: cover; }

This should fix the centering and resizing of the slideshow images.

Yesssss!! It works, all fixed now, finally we can continue to use your theme smoothly. Thank you for the code and the assistance .)

The option to set a thumbnail image should be right above “Thumbnail hover color”: https://i.gyazo.com/d38572e1cd673910e1c8a6630069dffe.png

If it’s not there then you can always create it manually in “Advanced Custom Fields”: https://i.gyazo.com/a89c90293cad868e29754f55af8573da.png

Please note that the image size should be 400×300 px or 800×600 px regardless of how the custom field is called (it’s called differently for backwards compatibility reasons).

it works now only with Gutenberg which means you cant disable it and use ‘classic editor’ also i am trying to add an external photo from Dropbox and it gives me a blank page what is the best way to load them remotely?

1. The theme has been updated to support Gutenberg and we’re testing it only with Gutenberg enabled. However, it should work also without it. Perhaps the custom fields are hidden in “Screen Options” in the upper top corner then?

2. Dropbox can’t be used as a hosting solution because they detect such activity and disable the resources that are doing that.

Furthermore, hotlinking may be disabled by default in Dropbox so perhaps that may be causing the blank page.

It’s best to upload your photos to your own server or to some image hosting solution.

Hello,

It seems that 1.x versions of the theme aren’t compatible with the current versions of WordPress.

Yes, updating to v2.5 would solve this.

Hi,

Where is the update data to 2.5? I can’t find it even if I log in, so please let me know.

thanks

Hello,

You don’t have a “purchased” badge so probably you bought it with another account. If that’s the case then you can download it using the other account.

As required by Envato Theme Check plugin now (this wasn’t a requirement before) all post types had to be separated to bundled plugins or our update wouldn’t have been accepted.

So, you can activate them in Appearance > Install Plugins.

We also had to separate the shortcodes and remove the SuperSlide editor.

We’ll be migrating shortcodes to blocks next to replicate the SuperSlide editor that way.

Thanks!

It sounds like you may be looking for a WooCommerce template.

In this template you can of course link the thumbnails to external pages (like products) but it doesn’t allow creating pagination.

You can have multiple portfolio pages though.

If you have many products then we would recommend that you stick to a template that is specifically designed for WooCommerce.

Your account has 0 topics and 0 replies. We’re using BBPress.

Can you please try again? Perhaps with a different topic title? Maybe you can post in another forum?

If that will not work then you can also email support@ikonize.com.

unfortunately its not working.

You can check with different account.

I sent email with purchase code. Thanks.

Yes, you can do that by adding “Additional CSS” like this:

.element { width: calc(100% / 6); }

Hello and thank you!

In Appearance → Customize → Additional CSS you’d have to add something like this:

.thumb-inactive { display: none; }

or:

.thumb-inactive { opacity: 0; }

There are new theme submission requirements in place and we’re planning to update our items to meet them soon (in January).

We’ll have a look at that slideshow.

It’s impossible to automatically play a background video on some mobile devices. They come with a fullscreen player and that’s the only way to play a video on some of them.

This slideshows will be redesigned to stack the slides one below another on smaller resolutions.

We intend to support videos on all devices but some have to have a different layout to make that happen.

The “Agency” label will not be displayed when it’s not specified so it’s enough to leave it blank.

Shortly, we will be updating both our items to support Gutenberg and then the mechanism for these custom fields will change to a Gutenberg block. This is expected to happen this year.

Our other item (Daisho) already offers this Gutenberg block and it allows any arbitrary labels. We will move it to Konzept in the near future as well.

That plugin inserts meta tags and it should work with any theme.

When you switch themes the meta tags associated with your content remain.

We satisfy this condition: https://kb.yoast.com/kb/does-yoast-seo-work-with-custom-post-types/ which you can check in /inc/post-type-portfolio.php.

Please provide a list of updates that you’d like to see implemented.

We recently updated our other theme to Gutenberg blocks and the new Envato requirements: https://docs.ikonize.com/daisho/repository.php Some of the modules that we prepared for that theme are planned to be transferred to Konzept (like the new demo importer or some Gutenberg blocks) but that isn’t planned to happen this or next month.

We’re preparing some other changes (like user voting for new features) which will enable us to operate more efficiently. This feature will become available within a short period of time.

Currently there is no shortcode that would allow this but you can create multiple portfolio pages, each with “portfolio template”.

Each can display a different set of portfolio categories (this can be configured in the page’s settings).

There’s no way to limit that to 8 projects in the page’s settings. You could edit project-loop.php: $post_per_page = -1; to 8.

We’re working on adding Gutenberg blocks to the theme and both shortcodes and page templates are expected to be replaced by them eventually.

This plugin isn’t going to work with the present version of Konzept because its portfolio template fetches projects only from “portfolio” post type.

But you can imitate this behavior (i.e. have multiple portfolio pages, each with different set of categories) using the “exclude/include categories” box in [Pages > (any portfolio page)].

Then for each project you can select “parent portfolio page” in [Portfolio > (any project)].

thanks for your quick answer!!