I can confirm the issue with prettyPhoto is caused by a bug in the theme. We’re going to release a fix for it on the next version, but in the meantime I took the liberty to add this code to your Custom JavaScript option, which should solve the problem by now:

Please let me know if this works fine on your side.

Regarding the problem you’re reporting with the “zoom” value for the Image component, that feature only works for images with original sizes that are larger than the available space to show them in the viewport. For example, if you include an image inside a 400px block, the zoom functionality is only going to work if that image is originally larger than 400px. Perhaps if you could point us to a specific image where the problem shows up, then we can take a further look at it.

We’re still looking at the issues you’re having with the galleries, so expect to hear from us soon.

Best,

Andrés.

Hi Jolyn,

Thanks for the follow-up. I checked your issue with image galleries, and for some reason there are images that are not being correctly aligned inside its container. I added this to your custom CSS to prevent it from happening:

The alignment for the contents of the Icon Box component can be controlled from the settings of the column that contains it by adding a special class name. The theme includes some helper classes called “text-left”, “text-center” and “text-right” for alignment purposes.

Please check this image for reference: https://www.dropbox.com/s/ur5s78emedo69y5/Screenshot%202018-02-21%2017.41.08.png?dl=0

You can also set the size and horizontal alignment of the column inside a row in case you need to use only one column (see the “Aspect” tab inside Column Settings).

The project gallery can be modified to have an auto-rotated gallery by overriding the template that generates its HTML code. For your specific case, you need to create a new file called gallery.php and put it inside the following location in your Child Theme: includes/plugin-integrations/nice-portfolio/templates/single-project (you may need to create that folder structure). Or just copy that file from the parent theme to the new location in your Child Theme.

Once you created the file, you need the following code inside of it:

The important part here is line 21, where we’re setting the slideshow value to “true” and its speed to 3000 miliseconds. You can change that last value to match the speed you’re looking for. The rest of the file is the same as the original template.

I also checked the page you reported as not being loaded on mobile devices most of the time, and didn’t find any issue, though the site in general is a little heavy on images (you may want to use some compression tool like WP Smush for that). If you could tell me what kind of device and browser you are using to load it, I can take a further look at it.

In the meantime, I’d recommend that you check if you’re seeing any kind of JavaScript warning or error in the browser’s console when loading that page (I’m not). If you are on the mobile version of Chrome, you may want to check Google’s article about remote debugging: https://developers.google.com/web/tools/chrome-devtools/remote-debugging/

A possible culprit for the behavior you describe is the full page loader, which may not disappear after the page is loaded when a JavaScript warning or error is triggered. So trying a different loader may help debug the issue.

Finally, I noticed that you updated the functions.php file of your Child Theme recently, and that caused the PHP code I added yesterday to be deleted, so the conflicts between Slider Revolution and your custom CSS are visible again. I’d recommend that you make sure to include that code again the next time you update the file.

Best,

Andrés.