Hello Phivos,

Can you provide us your backend and FTP access so we can have a better look on your issue here? By the way, seems like you are using an outdated version of Easyblog, can I upgrade it for you? Because we have addressed a lot of fixes in the latest version (5.0.17).

Yes no problem. Please see attachment and site details section. Please confirm that the site details section is not viewable by other users and that our details are secure. Thank you.

Regards,

Hello Phivos,

I've updated Easyblog for and the quickpost issue has solved. Please give it a try.

Dear Nik,

The problem persists. Please try to create a post through the quick post feature with a normal user account (not a super user account) and you will see the notification "unexpected token <". Try by logging in with:



Regards,

Hi Phivos,

It seems like there is some issue when users are not allowed to publish blog post from the ACL settings and I am able to replicate this issue locally. I will forward this issue to our developers and hopefully they will come up with the solution soon.

We are sorry for the inconvenience caused.

Dear Ezrul,

No problem. Let us know once you have an update. Thank you.

Regards,

Hey Phivos,

Can you download the attached file and upload it into /components/com_easyblog/views/quickpost/ and see if the problem still exists.

Dear Mark,

Thanks for the prompt reply. We uploaded the fix and it works fine through a computer.

But, we tested it on mobile phones (smartphones) as well. For normal text it works fine on the mobile phones. But, when we try to upload a photo via the quick post feature through a mobile phone, we receive the same notification "unexpected token <". Does this require a different fix?

In addition, we noticed that the "continue reading" buttons changed color from red-white to white-black after we uploaded the fix as you can see in the following link:
http://www.penaltara.com/blog
This is a minor issue for us and we include it herein just for your information. This is just what we noticed on our first interaction with the page after the upload of the fix. We have not noticed any other changes.

Thank you!

Regards,

Does this "unexpected token <" notification (that comes on the smartphones photo upload) relate to any photo size limit or format of the photo that is not accepted?

Hi Phivos,

I just tried the quickpost photo with smartphone and it seems like it works correctly. Refer my screenshot here, http://screencast.com/t/LoRnqnpN. Am I missing something here?

It looks great, but always the problems come up when a simple user uploads the photo. When you performed your test you were logged in with a super user account?

Please try to take a photo from your smartphone and log in with a simple user account i.e.
username: andreas
password: andreas

It seems that taking your own photo from your smartphone even if the format is jpeg it creates the problem. Did you face such a problem with other users as well?

Thanks!

Hi Phivos,

Yes I'm using andreas credentials just now in my previous screenshot above. Not really sure how to reproduce it as I'm not hitting any issue when uploading it through smartphone.

Dear Ezrul,

Thank you for the prompt response.

It seems then that the issue arises when we try to upload a photo taken by a smartphone (not a photo already found online) and upload it through a non super user account. We would like our users to upload their own photos taken by their smartphones (i.e. photograph their own experiences and places).

Can you try upload a photo taken by your smartphone through the following account?
username: andreas
password: andreas

Or this is not supported somehow? We cannot think of any possible obstacle. We tried with several smartphones.

Regards,

Hi Phivos,

I am really sorry for the delay of this reply.

Can you download the attachment below and place it inside your /administrator/components/com_easyblog/includes/quickpost/adapters/ folder and see how it goes?

Dear Ezrul,

No problem! We understand that some matters take time to trace the issue and fix it.

Unfortunately the problem persists. "Unexpected token <". Have you tried it with a smartphone yourselves?

Regards,

Hi Phivos,

I am able to replicate the issue and currently still investigate the issue. Since this issue is only occur on smartphone it will be quite hard for us to identify the exact problem of the issue. We will try our best and we will keep you updated once the issue has been resolved. Thank you for your kind understanding.

Dear Ezrul,

No problem. Take your time. Let's hope you will trace the problem at the end.

Regards,

Hi Phivos,

Thank your for your support. We will inform you immediately once we have found the solution to this issue.

Dear Ezrul,

Hope you are fine.

Any luck with the above?

Regards,

Hi Phivos,

I'm fine thank you . Regarding on the above, I believe the fix will be ready with the release of easyblog 5.0.20 later this week. Thank you for your kind and understanding.

Dear Ezrul,

No pressure. You've got amazing extensions and this smartphone usage adds even more value. Hopefully you will solve the problem.

We noticed that a similar problem arises once the user tries to upload a smartphone photo using the "new post" (not the "quick post" this time) feature. This time no notification pops up, but if we select a photo to upload the system does not finish uploading and it is like the system stacks while uploading - never ending the upload. This is not a big issue for us (from the moment that the "quick post" feature will be corrected) and we understand that from your side, perhaps you do not consider that the "new post" feature should have a smartphone usage and this is acceptable.

Regards,

Hi Phivos,

After a long debugging process on your site, we finally found out the exact reason that causing this issue on your site.

The issue is coming from php "imagecreatefromjpeg" function inside /administrator/components/com_easyblog/includes/simpleimage/simpleimage.php where this function will require a lot of memory in order to function properly. I've checked your site and it seems like you have set your memory_limit to 64M and the process to resizing image taken by a smartphone (13 megapixels in size) will require approximately 70M in memory to complete the process. You can check the link below for references.
http://www.dotsamazing.com/en/labs/phpmemorylimit

With that being said, I'm afraid that the only way to fix this issue is to increase memory_limit value on your server to a higher value so that the process can run smoothly without any issue. You can consult with your webhosting service provider and ask them to increase your current memory limit to 256M and see how it goes.

Dear Ezrul,

Thank you very much for your valuable input. The problem has been solved!

We ran many tests through various devices and the minor issue we face is that some photos are uploaded horizontally instead of vertically or the other way round, and so the photos are not displayed correctly like the photo in the following link that is vertical and displayed horizontally.
http://penaltara.com/blog/test-article-61

We understand that this more of a smartphone issue instead of a programming issue. Did you face such issue in the past?

Regards,

Hey Phivos,

Thanks for updating and I am glad that your issues are resolved now. As for the issues with the orientation, since these pictures are taken from your mobile device, it contains an exif data and if we were to write a compatibility layer for exif data, it might eventually require more memory and this is why we did not add this compatibility in it yet.

These images are actually saved on your devices in a different orientation but with the help of the exif data in the image itself, it allows the picture to be oriented correctly.

Dear Mark,

Thank you for the valuable support.

Regards,

You are most welcome Phivos