Reinstalling WP does the trick on Webkit-Failer Chrome. Didn’t reinstall Enfold at all.

You may work around those heavy loaded servers by setting it up correctly. If you use a CDN (external or own one) to deliver the static contents and if you’re able to configure the headers and expires of your webserver, it will grant you a real boost in performance. But overall if so many instances are running on a single (or clustered) machine, you should think about a different hosting plan. Saves a lot of time and pain… :)

After investigating the responses from your server… well… about 5 secs to get the DNS resolve… ain’t that good at all. After the resolve, your page loads within 3 secs, so this ain’t that bad at all. Maybe a phonecall to your provider could help also.

There are serveral ways to achieve this depending on your php skills.

Easy, but not that good idea is to copy all related files to the child so your modified iconbox.php will be loaded. You need to traverse this back to the file, where the shortcode is executed. In case of Enfold (individual framework) I wouldn’t recommend that.

Easiest way is simply modifying the original files and track the changes (file, linenumber, etc.). So it’s quite fast to readd the changes in a new version of the theme.

If you’re familiar with oop, you can write your own code straight into functions.php. In this specific case you should extend the avia_sc_icon_box class overwriting/redefining the shortcode_handler function. Be aware of the ShortcodeHelper reference (removing the wpautop).

And finally, if you’re familiar with jQuery, go this way. :) Create your own custom.js, append it to the footer, read out the href of each iconbox element and wrap whatever you like to have a link on.

If you’re talking about the repositioning, try to add some whitespace to the top and bottom of the image. Maybe 10 to 20 pixels would do the trick. Not by css, change the image itself. If you are aware of the pity image quality on mobile devices, generate several logos in different sizes. Place them into the media queries and you’re fine. :)

There’s no prob with Enfold overall. It’s by far the most advanced theme currently available anywhere with a custom framework (!). It’s got lesser options to mess around with compared to other themes, but this is for a good reason. Themes with custom frameworks (even those with some modified Options Framework fork) are quite a bit harder to understand than regular themes. The Avia Layout Builder is just one part and it is neccessary to render the page contents in a more or less different way than WordPress may support it with the core API.

Also, nesting objects is a tough part and Enfold doesn’t support this out of the box. It can be done, but I guess a lot of people will run in unpredictable probs with that. This doesn’t stick to Enfold, it’s a major hurdle on WordPress. Nesting plain and easy shortcodes is one thing. Processing serveral layers of shortcodes with dozens of attribs and layouted/formatted contents way different.

As a conclusion, you shouldn’t think about modifying an existing theme if you don’t have enough PHP knowledge. This raises furthermore, if the code is well shaped and object oriented.

As answer to this thread:
The blog can be easily modified by css. There’s no need to touch any of the source files at all. But by default, some views (selectable in builder) won’t provide a featured image in single view. A quick look at the corresponding file shows exactly, where the $thumb is placed and what to do. If you got some pretty much decent PHP/WordPress knowledge. As for the thumb sizes itself… well… Enfold generates a lot of different sizes. It’s easy to modify a existing or add a new thumbsize within functions.php.

Note:
You shouldn’t mess up your installation (and it is definitly messed up). Start fresh and always have a clean backup copy of the database. None of your so called errors/bugs occur on a newly installed WordPress with Enfold. Create a concept instead of messing around with features and stuff – this leads nowhere. Start easy and try to modify the simple tasks by css.

As a personal hint I would recommend using a real CMS instead of a sloppy and pity blog solution for your project. But this could be even more complicated…

Hey Axel,

most common things may be configured using a css declaration. So for the homepage you may try this:

.home .title_container {display:none;}

If you like to remove the html source, you may stick with the conditional is_home() and remove the output (which I currently don’t know).

But wait – I think you’re talking about the container holding the title of the page. Well, open up your homepage within the backend and have a look at the Layout section on the right. Just disable the header. :)

Regards,

Jörg

Hey,

what do you like to achieve?

Have a look to the answer in my topic from Dude: https://kriesi.at/support/topic/portfolio-sorting-options/

Do you like to have a full portfolio grid sorted by categories first and within each category then alphabetically? Doesn’t make that much sense because of the filter option…

Otherwise you could manually create pages and put the portfolio with selected cats on it. You may take a look here: http://kunden.formateins.de/kvm/hardware/ > Take a look at the subpages. Maybe it gives you an idea…

Regards