the_Alien_01

Thanks

Ok, that’s one heck of a plugin that the site you linked to is using. I queried the source a bit for plugin-traces, and then called our dear friend Google for help: it’s not Visual Portfolio but (of course) some paid plugin.

The bad news is: the behaviour that site is showing, is not by default in Visual Portfolio.
The good news however is: It definitely can be achieved. It will take some time, but is in fact not that hard. I guess you’d at least have to take the following steps:

• Find a lightbox-plugin to your liking
• Find some Gutenberg blocks that can help you with styling Portfolio Items as you want them to popup
• Create a custom Visual Portfolio list-template as per this short tutorial and make sure the links are constructed as requested by the lightbox plugin (if you don’t know PHP: don’t worry, re-use the snippets in the default VP-templates, the rest is plain HTML)
• Create some Portfolio Items using the blocks from the second bullet
• Create a Portfolio List that calls the Portfolio Items, using either the Portfolio or Post-based settings (so not Images)

The only thing you else might need is a special Portfolio Item-template without all the headers and footers and sidebars and such as a normal post-template would have. On that point the WP developer help-section might be able to help you.

As far as I can see it’s mostly choosing the right helper-plugins and some rather straightforward HTML-coding (with every now and then a bit of PHP).

• This reply was modified 4 years, 9 months ago by the_Alien_01. Reason: fixed the list
• This reply was modified 4 years, 9 months ago by the_Alien_01. Reason: changed the list to ul

Hi,
After updating WP and the plugin, ánd after increasing max_execution_time and memory_limit in php.ini things are working fine again.

Which of these solved the error is unclear, but it’s all ok now, so for now I’m happy.

Sorry for the delay:
I have a fresh qTranslate-X install, that means everything is in “[:en]English[:de]Deutsch[:]” style (and of course the Convert Database being set to the default don’t convert, since that’s what’s preferred by qTranslate-X).

By the way: I reported it as a bug to the Android mobile editor-crew as well. They confirmed they will check it while porting the iOS editor to Android, no roadmap though.

So maybe one day the problem will be solved…

Thanks, I’ll give that a try as soon as I’m out of deadlines and back to free coding.

Too bad. The conflict with the Android app still exists.

Thanks for the fast reply by the way.

Thanks

Hi there,
Nice feature.
How can I add my own parameter without hacking the plugin core?