Support community for TTG plugins and products.
NOTICE
The Turning Gate's Community has moved to a new home, at https://discourse.theturninggate.net.
This forum is now closed, and exists here as a read-only archive.
You are not logged in.
That should work nicely. Thanks.
Mark
Wow. Thanks all for starting this eye-opening discussion. The whole ADA thing had never even crossed my mind until now. Looks like I need to change a few things in my content. Although, good intentions aren't worth much in a world where anyone can sue anyone for anything including everything. "And so it goes..." as Linda Ellerbee used to say.
Mark
Thanx Daniel.
FYI this problem has been traced to a Wordpress plugin called Code Embed. Plugin worked until the latest Version of Wordpress. Am currently exploring other code embedding plugin solution. Anyone know of a good one?
Regards Mark
Thanks Rod, doing it now.
Don't think that's it. The images in the posts that are generating the errors don't have captions. I also see that error in a post with no images at all. I thought perhaps the code that creates the moveable focus animation in some of the images might be the culprit but those animations still work. That code, by the way, is Jeffrey Friedl's, and it is pretty cool. The posts with errors were written a long time ago before Gutenberg came out. Might that have something to do with it?
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 68 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 146 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 230 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 79 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 80 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 153 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 233 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 82 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 84 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): ID myplayer2 already defined in Entity, line: 127 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 171 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175Warning: DOMDocument::loadHTML(): Unexpected end tag : p in Entity, line: 87 in /home/markho6/public_html/blog.photophart.com/wp-content/themes/backlightpangolintheme/inc/theme_posts.php on line 175
These are old blog posts that have been on my blog a long time, have not been changed or edited and were working fine. Now suddenly they are not. Any idea what might be going on here?
They seem to start here: https://blog.photophart.com/?p=848
Regards Mark
Maybe make a WIKI.
https://en.wikipedia.org/wiki/Wiki_software
Following Ben's instructions my original issue seems to be resolved.
Thanks guys! You're great, as always.
Mark
Got it. Update 2.0.9 shouldn't negatively impact non-wordpress sites then?
I have restored the pangolin wordpress theme in its entirety from a backup copy. The problem goes away completely. So the pangolin theme is getting mangled by the 2.0.9 update, or at least it seems that way.
Blog is the only thing I've updated to 2.0.9. Blog is in it's own domain and backlight resides there with it. Site worked great until the 2.0.9 update so there must be something screwy with one of the modules that were changed as nothing else was modified. I'm examining ways to backtrack to the site's state before the update. Looks tricky.
The theme is exported from the blog's domain not the main domain. What steps are you referring to after exporting? I use a child theme to link the exported pangolin theme.
Backlight2 WP module is at 2.0.3. Tried exporting the theme again. No idea where that 700 px width is coming from as I don't have that set anywhere that I can find. Perplexing.
It appears that all my page settings are the same in the page template but my site appears to be about tablet size width on a desktop display. Pretty sure that's a setting somewhere but I can't find it.
Regards Mark
ooops: affected site is at https://blog.photophart.com
It should look like this: https://blog.photophart.com/testblog/
Thanks Rod. Have done the same.
Does BL2 in Wordpress still use the Mobble plugin? Wordfence is telling me Mobble appears to be abandoned and should probably be gotten rid of.
Regards, Mark
Slogging through the possible things that I've seen cause this type of problem in Backlight and the previous CE products I finally got to cart shipping. Lo and behold the culprit stood before me in bright red letters. Standard shipping, enabled and default was listed as "incomplete". Hadn't checked it before because I knew it was complete. Indeed, had to be complete for everything to work. In this case, however, shipping pricing on Packages had been reset to nulls. I'm quite sure all those empty slots had entries in them, but they were gone. Anyway it was quick work to re-enter the data that had been there because clicking the empty box opened a drop-down revealing the number that had been there previously. I'm still checking all the albums but on the surface it appears the pricing schemes have returned and the problem is solved.
Regards, Mark
Template set for mixed pricing. Albums are set to use default pricing scheme. Default scheme uses several different print sizes and digital DL. Many other pricing schemes are available and are assigned on a per photo basis. And all of this was working perfectly until the update to 2.0.7 .
Examination of the tables shows the pricing schemes assigned to the photos are still there. Apparently, BL isn't seeing the pricing scheme in the tables. Since this has happened to every single image in every album in every directory that might be diagnostic of what's gone bonkers.
Have tried resetting cart. No go. Tried Update Album Files. No go. Republished an album again. No change. All images have been changed to a pricing scheme of digital download only and they can't be changed.
Rod, wrong site. Try https://markhoffmanphotography.com
Further exploration reveals that every image on my website has had its pricing scheme changed to digital download only, even the albums where no image rearrangement was done. Sadly, this includes all my client albums as well. Rather a bad situation.
One item more: republishing the images doesn't help. The pricing scheme is not being uploaded.
Any chance you can send me a link of some sort to backtrack to the previous version of backlight? The one before 2.0.7
I'd really like to fix this ASAP and the previous version was working great, albeit without photo rearrangement capabilities.
Mark
Love the photo arrangement option but all my pricing schemes have changed to digital download only. Um, we're talking hundreds of images. Haven't tried republishing yet. Is that a step that needs to be done after rearranging images?
Mark
Didn't realize how much I really wanted to be able to do this. Simple. Functional. Useful. Nice. Yeah, yeah, I know. Too many superlatives.
Regards, Mark
Any further behind-the-scenes activity on this topic?
Mark
Tried one other check to make sure the pricing data was actually in the category field in metadata by using Jeffrey Freidl's online metadata viewer and his tool confirms the metadata is correctly in the image file.
Mark
Excellent idea Rod but, yes , mixed pricing is enabled. Mixed pricing was working when the album was originally published from Lightroom a couple months ago.
Mark