amm82

I don’t follow why the documentation uses “page?value”

However I can verify that:

https://site.com/page1/?param=value

where the form is on “page1”

is a working structure

thanks again. I look forward to using it and I’ll ask my company to spare a small donation to you.

incredible! I know we will get a lot of use out of this. We will use it to build several galleries of student artwork each year. Thank you very much! A donation is coming your way.

thanks for your thorough response.

just so we’re clear, regarding Description, it would be helpful to be able to map both Title and Caption together to Description. That way, I could quickly populate description without manually entering html for each. Description appears in my lightbox.

In my specific case, if this were possible I would first add Title and Caption on separate lines, then I would go into each image Description and enter further details.

Another wrinkle: I begin all of my Descriptions with a linebreak so that the first line of text begins below nav controls in the lightbox. I guess I could add clear:both to the nav to accomplish the same thing.

The end result I’m going for is
Description:
linebreak
<<title>>(unique css class?)linebreak
<<caption>>(class?)linebreak
additional manual entry here.linebreak
linebreak

This might be a common use case. Think of an art gallery
title-year
artist
medium
blurb

thanks again

same as jayque9. glad dev is aware. thanks

Hi, in my case, this turned out to be a plug-in conflict, and was able to deactivate the plug in, then activate jetpack, then reactivate the plug-in. No conflicts so far.
The conflicting plug-in was intense shortcides, but don’t know why. Someone suggested it could be its handling of nonces.