Grumbledook

Amazing, thanks Arno.

I’d assumed that the lens name was included in all the exif. I just updated the plugin on the new site I’m working on and I’ve got an old image on there from my Canon 40D and it’s now displaying the lens used.

It’s also kept the ?? symbol.

Much appreciated!

Hey zerodegreeburn,

My first post in this thread shows the settings I used to get it working on woocommerce.

Yeah they look exactly the same to me so I’d expect it to work on both. I’m all out of ideas sorry.

Both links are the same page…

Hard to say without looking at your site and seeing what the css id and classes are. Those are the settings on my blog page (I don’t have them on the front page) and it’s the default untouched canvas template.

Only thing that it may be is if you have the pagination settings not set to numbers in the theme settings?

Just upgraded another of my sites using canvas to 5.2.7 and my own custom child theme.

Canvas Theme Options -> Display options -> Pagination Style set to Numbers

Inf Scroll settings:

#content #main
.woo-pagination
.woo-pagination a.next
.post

This works fine on my site.

I don’t have any posts on my install right now to test it with, only products with woocommerce products. If I manage to get some time to test it out I’ll try and remember to report back.

I’ve got it working on woocommerce using canvas so this may work (I’ve got the canvas pagination settings set to numbers not next/prev though:

#content #main
.woo-pagination
.woo-pagination a.next
#content div.post

This is what works for woocommerce, so tinker if the above doesn’t work for posts.

#content #main ul.products
.woo-pagination
.woo-pagination a.next
ul.products li.product

I’ve also been getting it for the last day since upgrading the plugin…

Thanks, I’ll try and contact photoswipe directly.

A further update, the new field I added doesn’t seem to work on the front end.

It is just adding an empty span.

<div class="clone_username field-item  two-third">
	 <div class="field-shell">
	 	<div   class="single-text">
	 		<span   class="" >
			</span>
		</div>
	</div>
</div>

It does this on both the profile page and on the profiles listings page. As I said in the previous post it may be down to the fact when you go to edit the profile, that new field I added doesn’t save what you added before…

Somehow I totally missed the Fields section in settings.

I just created a new Username Field using a textbox and set it to not create multiple fields on the forum builder.
However if either the admin or the user goes to edit the profile, the field comes up empty. Shouldn’t it fill it in with the current saved setting? All the default fields seem to retain the data.

Is it also possible to get a users wordpress user id number to display in a field?

It appears it isn’t just the menu that it affects.

I’ve also added some woothemes “tabs” on both the post and the sample page.

The menu doesn’t work on the homepage.
The menu and the tabs both work on the post (which has a nextgen gallery)
The menu and the tabs don’t work on the sample page (has no gallery)

This also happens with Woothemes main Canvas theme too.

Bit more info, the menu on pages where photoswipe has replaced the lightbox, the menu is working fine. On all other pages though the menu doesn’t work.

This also happens on a desktop browser if I set it to always replace and make the window smaller to get the “mobile menu”. The home page the menu doesn’t work, on the post with a gallery the menu does work.

https://unseeingeye.com/test/ (I may do more tinkering in the mean time)

There is also another thread with the same issue https://www.ads-software.com/support/topic/mobile-iphone-menu-eaten-when-using-photoswipe-for-nextgen-plugin

Given that it works on the post with a gallery but not the rest I would think it was due to the plugin rather than the theme. I would be surprised if a large theme company like Woothemes who wrote the wordpress menu system would be doing something non standard too.

I’m happy to help out in any way I can, though I’m not much use with the inner workings code wise.

Cheers shauno,

That’s something I doubt I’d ever have worked out if I’d come into a problem with it. So you change to the if statement just checks that there is something in the field correct?

I don’t know if anyone else has mentioned it, but they also work if you use a gallery made up of nextgen image tags as well which is really helpful imo.

Was really pleased to find you had made this plugin, I was thinking over the weekend the easiest way I could implement my idea was if nextgen had custom fields. I was about to email alex about implementing them but thankfully a quick google for them before I did showed me you’d already done the job!