Hi Simon,
I could not replicate this locally. May I know what were the exact steps you used to create the blog post?

It wasn't me who posted it however the client is fairly experienced at blogging and has been doing so for a while.

I checked with them and they posted it from the backend as normal, rather than the frontend. Other than that everything else seemed to be completely normal. They also reported that some users (one includes Valts.grintals@delta-ee.com) got multiple notifications, up to 5?

I am on their list and only got one copy, however.

It seems like you have enabled to use "Send E-mails During Page Load" this is one of the reason why it send out multiple email to the same user.

What my suggestion is setup cronjob from your server so it will send out those pending email in certain minute.

If you can provide us with your Cpanel access so we can help you setup on this.

Regarding with your main issue, I've checked from your backend Easyblog email activity page, it seems like no more any emails so that was difficult for us to trace back what happen on previous emai, can I have the permission submit a test post from backend? Before i submit a test post, I will temporary turn off all the send out to subscriber setting from backend, so it will only send to site admin and custom email address.

No problem I an set up a cronjob instead. What sort of frequency should I set for that so as not to overload the server but also to ensure prompt delivery of notifications?

Where should I insert the secure details for the cpanel?

You can provide us with your Cpanel access at http://stackideas.com/dashboard/site , I would suggest to set every 5 minute for the cron interval and send out 20 ~30 emails.

Updated now and that's fine to do what you need to do to test, as long as no notifications go out to site subscribers (admins are fine, however)

Hey Simon,

It seems like there got 2 issues :

1. Blog permalink included /administrator URL
>> I already applied some fix in this file JoomlaFolder/administrator/components/com_easyblog/includes/post/post.php and this fix will included in next release version as well.

2. Unable to retrieve the correct menu item id from Sh404sef if publish a new blog post from backend
>> And this issue it seems like not coming from us, but I already applied some code in this file JoomlaFolder/administrator/components/com_sh404sef/sh404sef.class.php , it should show the correct blog permalink now, can you give it a check?

Thanks Arlex - so for the first one, was this just a bug in Easyblog or something we had done?

For the second one, since this change was made to sh404SEF does this mean that it'll be wiped out if/when we upgrade? Should i notify the developer and was it a bug from their side of things or something which meant that Easyblog and it weren't talking together properly?

Also I set up the following cronjob:

/bin/wget -O /dev/null "https://www.delta-ee.com/index.php?option=com_easyblog&task=cron"

However currently I get the following response via the email notification I set up:

/bin/bash: /bin/wget: No such file or directory

I did check with the host about the wget path as detailed in your documentation to verify that it should work okay. Any ideas?

Thanks Arlex - so for the first one, was this just a bug in Easyblog or something we had done?

You're welcome.
Yes, this fix will included in next release version as well.

For the second one, since this change was made to sh404SEF does this mean that it'll be wiped out if/when we upgrade? Should i notify the developer and was it a bug from their side of things or something which meant that Easyblog and it weren't talking together properly?

I believe one of our customer already reported this to them, you can refer on this thread -> https://stackideas.com/forums/bug-with-api-twitter#reply-324017 , but it seems like our customer don't have time to follow up that case, based on what my last replied from that thread.

Regarding with your Cronjob issue, if your server did support Wget, perhaps you can consult with your webhosting provider what is the correct Wget path from your server? And you can try this following cron command and see how it goes?
[gist type="php"]
/usr/bin/wget -O /dev/null "https://www.delta-ee.com/index.php?option=com_easyblog&task=cron";
[/gist]

Thanks Arlex, that last tweak to the comand seemed to work, at least this time I got the following content in the notification email:

--2017-06-21 10:30:01--  https://www.delta-ee.com/index.php?option=com_easyblog&task=cron

Resolving http://www.delta-ee.com (http://www.delta-ee.com)... 185.123.96.206

Connecting to http://www.delta-ee.com (http://www.delta-ee.com)|185.123.96.206|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: unspecified [text/x-json]

Saving to: '/dev/null'



     0K                                                        81.8M=0s



2017-06-21 10:30:02 (81.8 MB/s) - '/dev/null' saved [728]

Does that all look okay to you?

Looks like quite a bit of info to take in on that other sh404SEF-related thread so I'll need to mark that for me to go over properly when I get a chance!

Yes, this response show is connected, perhaps you can try set your Cronjob time interval and test the email notification.

Looks like quite a bit of info to take in on that other sh404SEF-related thread so I'll need to mark that for me to go over properly when I get a chance!

Alright.

Hi Arlex

The response i quoted there *was* from the notification email so it looks ok to me. I had to set the run time to 30 mins instead of the suggest 5 mins purely because Siteground won't allow cronjobs to run any more regularly than that.

Thanks again.

You are most welcome Keep us updated if you need any further assistance in the future.