Reply To: Portfolio issues with conversion to HTML5

I actually meant that entire section of code from the top to bottom needs to match the latest updated version. And then double check to make sure the portfolio template is exactly the same as the latest version as well.

I’m not referring to just that particular line of code, but the whole thing. The reason is because there were a few things changed for 2.0, and if you’re using the HTML5 markup and don’t add in all of the changes then it probably won’t work.

Is it possible for you to temporarily replace the entire functions and portfolio template with the new versions so you can see that it works? Then you could add in your other custom code manually and do a test each time to make sure none of it is conflicting with it. Does that make sense?