Hi Vincenzo,

I am sorry for the delayed reply.
Can you provide us with backend access and FTP access so that we can assist you further on this issue.

Please advise.

Done, via email.

Thanx.

Hello Vincenzo,

THanks for getting back to us,

I have replied on your ticket #35221 please have a check.

Sorry, already done!

Hello Vincenzo,

In the future, kindly please do only stick to 1 support channel when you are requesting for support. This would ensure that your issues are assisted swiftly

Hello,

after a couple of days, after your support, I tried to test if the issue has been fixed, and it was so!
I could create a new post frim frontend dashboard.
Today I'm writing a new post in the blog and the problem still remain...
What did you do last time? Why it continue to not working fine? What's the problem in this?

Thanks and regards.
Vincenzo.

Hi, I think I found the issue...

the dashboard.write.php script has a call to function ( ejax.dialog(...) ) having arguments that seems was uncorrectly written...
After commented, all seems to work fine. I'm not a programmer but I suppose that problem consists in a wrong argument passed mode, maybe the "{" "}" ?

following the code:

ejax.dialog( {

				title: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_CATEGORY_DIALOG_TITLE' , true );?>',

				content: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_CATEGORY_ERROR' , true );?>'

			});

and the other one:

ejax.dialog( {

				title: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_TITLE_DIALOG_TITLE' , true );?>',

				content: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_TITLE_ERROR' , true );?>'

			});

Please could you give me the right code, thanks and regards.

Hello Vincenzo,

I am really sorry for the delay of this reply as it is a weekend for us here. To be honest I am not really sure what has been modified but the codes that you have posted above seems to only kick in when you did not choose a category to post your blog post into.

What errors do you get and how do I reproduce this? Is it possible for you to provide us with the back end and FTP access to your site to check on this issue?

Hi, thanks for reply me\

It seems so. When loading page with chrome in devlopment mode, it reports a syntax error on that line.

ejax.dialog( {
title: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_TITLE_DIALOG_TITLE' , true );?>',
content: '<?php echo JText::_( 'COM_EASYBLOG_DASHBOARD_SAVE_EMPTY_TITLE_ERROR' , true );?>'
});

like as the argument passed to ejax.dialog() function have a syntax error, and when I comment the execution of that function all seems to work fine and I can publish my article via frontline dashboard.

Anyway I supply you the date request in Site Details tab.

Thanks

Hello Vincenzo,

The FTP access which you have provided isn't working. Can you please advise?

Sorry, try again... thanks. I've updated data in Site Details from last post.

Hello Vincenzo,

Hm, it looks like both the site's username and ftp doesn't work. Could you please post them again below?

It's strange... I try again...

I've just tried ftp access from terminal and the user and password work good...

Please let me know

Thanks, the access works now but I don't hit any errors when posting a new blog post on the front end. How do I replicate this issue? This is what I am getting upon posting a new blog post on the site, http://screencast.com/t/omupDoWk9

yes, of course, because, you can double check, I've commented the call to that function in the script I've indicated. If you remove the /*... */ commented mark you can notice that button doesn't work because of the error of the browser at that line...

Can you please remove any comments or any changes on the site so that I can reproduce this error?

Ok, I've just removed my comments in the script... and after made a check, the button doesn't work again...

thanks for you support

Hello Vincenzo,

The issue here is because of your language string http://screencast.com/t/peuJQTzP . There is no way to escape this and you shouldn't use htmlentities for ' . I have changed the unicode character into ' and it works fine now.

Thank you so much, I've understood the issue, checked the fix, and it works fine now! Thanks again for your support!

Cheers.

Thanks for updating, glad that your issues are resolved now