Closed GoogleCodeExporter closed 9 years ago
BP Album versions 0.1.7 and 0.1.8 have a very primitive activity stream posting
system. To get the picture to appear, you must go into the picture's 'edit'
stream, ensure "post to activity stream" is set to 'yes', and click 'save. At
this point, the picture should appear.
Version 0.1.9 has a far more sophisticated activity stream posting system with
image grouping and privacy controls. So we're probably not going to fix this
defect before the 0.1.9 release unless we have to go in and do an emergency fix
for something else.
Original comment by CarlRoett@gmail.com
on 28 Sep 2010 at 10:10
[deleted comment]
@CarlRoett
Thanks for such a kind and thoughtful reply! Much appreciated.
However, please note that this issue was a path problem, seemingly because of
the 'remapping' feature not having been applied to the activity stream. Even
when the picture's 'edit' stream was already set to "post to activity stream"
and the code to show the pic was being used, the picture did not show because
of a bad path.
Speaking of which, the plugin should /accept/ differences between physical path
and virtual path, and use the latter. If that was done, then the remapping
feature would not be needed.
Sure, the plugin has to grab the physical path to place the file. But then (it
would seem) when the plugin asks WP for the virtual path, the choice is not to
use it. Instead either a web root indicator (/) or the full domain name -- is
placed at the beginning of the physical path, and that is attempted. On most
servers that is a bad path.
Placing either a web root indicator (/) or the full domain name
(http://blah.com/) at the front indicates the path that follows /should/ work
in a browser for public service. Yet the elements of the physical path that are
being stuck in are usually unacceptable in the browser path.
I really appreciate that the activity stream options are being worked on, but
this is a path issue, and enhancing the activity stream options alone won't
truly resolve the path issue (although enabling the remapping fix could serve
as a good band-aid). I hope a better approach to the path issue will be
considered in the newer versions.
All in all, this plugin is the only one I could get to work with the latest
versions of WP and BP -- out of trying out all that I could find. So I am
thrilled with it, even if slightly imperfect. I am currently using .htaccess to
restore the path back to what it needs to be. Thanks again for replying. Much
appreciated!!
Original comment by douggjos...@gmail.com
on 28 Sep 2010 at 6:39
@CarlRoett
A thousand pardons. Earlier when I read your reply, I mistook it to mean you
thought the defect was a user-interface issue instead of a path issue. I see
now that you recognize the defect (path issue) as distinct from the
user-interface concerns, and you're simply saying a fix will likely be delayed
until a new version. Sorry about that.
Original comment by douggjos...@gmail.com
on 28 Sep 2010 at 7:40
Original issue reported on code.google.com by
douggjos...@gmail.com
on 28 Sep 2010 at 10:01