After some effort I think I have found a partial solution to using News Pro with Easyblog5.
I have had many issues with NewsPro not picking up the image from the blog. This is ONLY AN ISSUE when the image is the Cover Image or the Blog image. If the image is embedded as the first image in the blog text, all is good.
I first had problems when I upgraded even posted a problem, but I thought the issue was solved however it was just masked because all works well if the image is the first one inside the blog text.
The fix can be done by hacking News Pro and the code in t/modules/mod_news_pro_gk5/tmpl/com_easyblog/view.php around line 21 where the code checks to see if there is a path in the image field of the easyblog_posts table. If there is a path it means there is a cover image.
For me there are two problems.
Case 1
The blogs were imported from a previous version of Eastblog and I did their upgrade. Even with the latest version of NewsPro I did not get cover/blog images. If I looked in the path of the image file stored in the easyblog posts table it was of the form user:ID/imagename.jpg, in my case user:991/imagename.jpg would be typical.
I see the code in the current NewsPro looks for the string post: and removes it with a string replace on about line 26. I changed it to replace user: and that helped clean up my path.
Case 2
Same issue above but my images were stored in the folder images/easyblog_image/ not the images/easyblog_articles/ which is the current easyblog default. So I also had to change the path that is added on line 28 to be the same as mine and what I had set in the easyblog media settings.
Case 3
This was a big deal to find. If the easyblog installation is default, the media settings have the shared folder set to images/easyblog_shared/ if you use this option and allow users to store media in it and they post that media as the cover image, again NewsPro does not pick up the images. The problem is that the path easyblog chooses to put in their table has the form shared/imagename.jpg and somehow NewsPro is supposed to change to replacing shared/ with easyblog_shared/. At first I was about to hack the view.php file to test for the new case and replace shared/ with easyblog_shared. But I found a simpler fix.
I moved all my images from images/easyblog_shared/ to images/easyblog_articles/shared and changed the shared directory path in the easyblog media settings to match. Now my images show up and the NewPro code only needed the post/user hack. Now if you have a lot of shared media files embedded in the blog text this fix will break them, but for me I was in the upgrade test phase so not an issue.
Future?
Well somehow I think there is more to this, easyblog probably has more cases for file paths that get put in their blog table, I do not think NewPro coders made up the post: case. But for now this fix is stable.
I do think easyblog coders could just put the real image path in their table. Would help us all.
I also worry that it seems easyblog puts the full site path into the blog text when you put a shared image into the blog text. This will cause me all sorts of problems whenever I move a site.
I have had many issues with NewsPro not picking up the image from the blog. This is ONLY AN ISSUE when the image is the Cover Image or the Blog image. If the image is embedded as the first image in the blog text, all is good.
I first had problems when I upgraded even posted a problem, but I thought the issue was solved however it was just masked because all works well if the image is the first one inside the blog text.
The fix can be done by hacking News Pro and the code in t/modules/mod_news_pro_gk5/tmpl/com_easyblog/view.php around line 21 where the code checks to see if there is a path in the image field of the easyblog_posts table. If there is a path it means there is a cover image.
For me there are two problems.
Case 1
The blogs were imported from a previous version of Eastblog and I did their upgrade. Even with the latest version of NewsPro I did not get cover/blog images. If I looked in the path of the image file stored in the easyblog posts table it was of the form user:ID/imagename.jpg, in my case user:991/imagename.jpg would be typical.
I see the code in the current NewsPro looks for the string post: and removes it with a string replace on about line 26. I changed it to replace user: and that helped clean up my path.
Case 2
Same issue above but my images were stored in the folder images/easyblog_image/ not the images/easyblog_articles/ which is the current easyblog default. So I also had to change the path that is added on line 28 to be the same as mine and what I had set in the easyblog media settings.
Case 3
This was a big deal to find. If the easyblog installation is default, the media settings have the shared folder set to images/easyblog_shared/ if you use this option and allow users to store media in it and they post that media as the cover image, again NewsPro does not pick up the images. The problem is that the path easyblog chooses to put in their table has the form shared/imagename.jpg and somehow NewsPro is supposed to change to replacing shared/ with easyblog_shared/. At first I was about to hack the view.php file to test for the new case and replace shared/ with easyblog_shared. But I found a simpler fix.
I moved all my images from images/easyblog_shared/ to images/easyblog_articles/shared and changed the shared directory path in the easyblog media settings to match. Now my images show up and the NewPro code only needed the post/user hack. Now if you have a lot of shared media files embedded in the blog text this fix will break them, but for me I was in the upgrade test phase so not an issue.
Future?
Well somehow I think there is more to this, easyblog probably has more cases for file paths that get put in their blog table, I do not think NewPro coders made up the post: case. But for now this fix is stable.
I do think easyblog coders could just put the real image path in their table. Would help us all.
I also worry that it seems easyblog puts the full site path into the blog text when you put a shared image into the blog text. This will cause me all sorts of problems whenever I move a site.