Sam Rohn

panopress is NOT a viewer itself but is a method for embedding viewers like krpano, and stereo VR etc would be a function of the viewer, not panopress

sam

panopress is working fine for me with all versions of wordpress from 4.0 through the latest 4.6.x, including 4.5.3

• This reply was modified 8 years, 2 months ago by Sam Rohn.

yes, panopress is compatible with wordpress 4.4.2, no specific issues have been noticed or reported

video metabox metabox is obsolete in version 1.0.5

select video post format, and add the url to your video at top of post above more tag like so

https://www.youtube.com/watch?v=4FXhLERZW4I
<!--more-->
article text goes here, etc...

see this post on fukusawa theme authors blog for more info –

https://www.andersnoren.se/upcoming-changes-to-my-wordpress-themes/

sam

yes, panopress is fully compatible with wordpress 4.3+

i tried this control+v biz on my own s2 protected site, and it did NOT allow access to protected pages

so it would seem this is a false alarm

this is now working as expected in amr users version 3.21 without my functions.php code above, no more broken page 2 queries

thanks again ??

sam

replace the double quotes in the href surrounding the shortcode with single quotes like this

href="[shortcode var="foo"]" = bad

href='[shortcode var="foo"]' = good

so your code would end up like this

<a href='https://isec.solutions/members/[s2Get constant="S2MEMBER_CURRENT_USER_LOGIN" /]/profile/'>My Account</a>

this is due to changes in wordpress 4.2.3 shortcode api, see this post for more details

Changes to the Shortcode API

also note that you will need to enable shortcodes in widgets if you have not already done so, put this code in functions.php to enable shortcodes in widgets

add_filter('widget_text', 'do_shortcode');

sam

this code is exactly what i was looking for, thanks ??

ok, i just tested on my (slightly out of date) original dev site which is still on amr+ 2.1.2 and pagination URLs works fine over there, so it must be something i recently added to live site, i will backtrack a bit and report back when i have more info…

thanks again ??

sam

i am actually co-dev on another wp plugin (panopress), i spend half my support time telling other people to disable plugins and test w default theme etc, but before i follow my own advice i want to look through my own code here and see if this error is my own fault ??

ok, i found a simple workaround for now, but i will continue to investigate the actual cause of this error

the following code in functions.php will convert “#038;” to “&” in urls, and restored my broken pagination functionality

// Fix URL Ampersand Problem : "#038;" replaces "&" and breaks pagination urls

function amp_url_bugfix($link) {
return str_replace('#038;', '&', $link);
}
add_filter('paginate_links', 'amp_url_bugfix');

search google for “wordpress #038; pagination error” for more info, there are a few topics for a few different plugins w same issue floating around

sam

it seems that i was actually using amr users plus 2.1.2, i have now updated to 2.1.4, i also rebuilt the list cache, re-saved amr settings, re-saved wp permalinks, and rebuilt site cache (zen cache), empty browser cache etc, but the same error persists…

(i am also using amr users plus s2member 1.2, if that is relevant)

the fact that the “&” right before “country” is being mangled while others in the same string are ok is a clue i suppose, “country” is actually custom user meta i coded myself, so perhaps this error is caused by my own code somewhere…

otherwise, i have a lot of other plugins and custom theme and lots of custom plugin code running on that complex membership site so mass-deactivate for troubleshooting is something i hope to avoid, but i will try to narrow down a list of suspects, and i will report back when i find the culprit

grazie

sam

i suppose the option would have been to announce that there was a major vulnerability in WP, but it would not be patched until all plugin devs have a chance to review and update ?

a few or even a lot of broken shortcodes is preferable to being hacked imo, wp dev team privately notifying all plugin devs in advance is the same as making a public announcement of an un patched vulnerability (word will get out to the wrong ears somehow), and leaving it that way while waiting could be risky…

i guess concerned plugin devs should subscribe to wp security trac or whatever, and wp devs should have at least sent an email notification after 4.2.3 release to all plugin devs to review their code…

reverting to 4.2.2 is not a good idea, a hacked site is bigger headache than a few broken shortcodes…

here is an easy fix, this resolved WP 4.2.3 breaking some s2member shortcodes on one of my sites, the same principal should work for similar shortcode usage with other plugins

use single quotes ‘ for html attributes surrounding the shortcode, and double quotes ” for the shortcode’s own attributes

like this

a href='[shortcode value="foo"]'

NOT like this

a href="[shortcode value="foo"]"

sam