I was wondering if you had any plans for making the management of the emails a little easier? We have a customer that will be sending around 80 emails a month (probably more) which will make the tree fill up quickly. Could you group the emails by month/year (or add some form of custom foldering)?
I'll add this to our backlog and maybe we'll include something to fix this issue in an upcomming release - if this really urget for you I would be happy to share our code for the TreeController so that you could write your own solution based on that one and swith to use your own Tree.
Yep shoot it over. What do you use for data access? We're going to have to modify that and also the one for the lists folders as they're already getting a little out of hand.
I guess you'll have to change the namespace and reconfigure the "/config/trees.config"-file to use you new controller instead of the core-controller.
The data access is done using a custom peta-poco implementation. When we released Newsletter Studio the data-stuff in the core was not public so we had to make something on our own.
You can access the repository using:
var repo = GlobalFactory.Current.NewsletterRepository
But depending on what you are trying to do - you might need custom fields on the ns_Newsletters-table and in that case I would just create something custom in the controller to fetch the letters.
If you need any details or help with details, please send me an email: markus [at sign here] enkelmedia.se.
And also - if you would like to share your solution for our inspiration in upcoming releases - please send me an email =D
We've put together a quick month/year grouping which seems to work pretty well, we'll send over the code if you can ping me an email [email protected]. The main issue is we're having to filter based on month/year in memory which would be better through the repo but I couldn't spot a filterable method.
Can you send over the code for MailingListTreeController as well please so we can set those into folders (if not, no worries).
Thanks for sharing the code and the solution! What a great blog post as well!! So cool! Great work! Thank you!
I see reg. the issue with the in memory sorting, I guess that is not a huge issue at the moment - but if you really need to sort on the db-level you could just use peta poco to do so. The core does not have any methods for sorting on date at them moment - But I would say that we're honting millisecounds here =D
Thanks your engagement with this =D If people find this way of sorting the newsletter good I might be something that we add as an option i future releases.
Folders for emails?
Hi guys,
I was wondering if you had any plans for making the management of the emails a little easier? We have a customer that will be sending around 80 emails a month (probably more) which will make the tree fill up quickly. Could you group the emails by month/year (or add some form of custom foldering)?
Cheers,
Tim
Hi Tim!
Thanks for sharing a good idea!
I'll add this to our backlog and maybe we'll include something to fix this issue in an upcomming release - if this really urget for you I would be happy to share our code for the TreeController so that you could write your own solution based on that one and swith to use your own Tree.
Let me know =D
// m
Hi Markus,
Yep shoot it over. What do you use for data access? We're going to have to modify that and also the one for the lists folders as they're already getting a little out of hand.
Thanks,
Tim
Hi!
This is the code for the tree controller: https://gist.github.com/enkelmedia/648baa5587b702585193505b39b8b7fa
I guess you'll have to change the namespace and reconfigure the "/config/trees.config"-file to use you new controller instead of the core-controller.
The data access is done using a custom peta-poco implementation. When we released Newsletter Studio the data-stuff in the core was not public so we had to make something on our own.
You can access the repository using:
But depending on what you are trying to do - you might need custom fields on the ns_Newsletters-table and in that case I would just create something custom in the controller to fetch the letters.
If you need any details or help with details, please send me an email: markus [at sign here] enkelmedia.se.
And also - if you would like to share your solution for our inspiration in upcoming releases - please send me an email =D
Cheers!
Hi Markus,
We've put together a quick month/year grouping which seems to work pretty well, we'll send over the code if you can ping me an email [email protected]. The main issue is we're having to filter based on month/year in memory which would be better through the repo but I couldn't spot a filterable method.
Can you send over the code for MailingListTreeController as well please so we can set those into folders (if not, no worries).
Ta
Tim
Don't worry about sending over the code Markus, I refactored the code last night -seems to work well.
I've posted the month folder logic on my blog here for anyone that's interested: http://thesitedoctor.co.uk/blog/group-newsletter-studio-newsletters-by-month-in-the-umbraco-backend-tree/
I'll post the MailingList one in the next few days.
Tim
Here's a post from the future... :)
http://thesitedoctor.co.uk/blog/group-newsletter-studio-mailing-lists-by-name-in-the-umbraco-backend-tree/
Hi!
Thanks for sharing the code and the solution! What a great blog post as well!! So cool! Great work! Thank you!
I see reg. the issue with the in memory sorting, I guess that is not a huge issue at the moment - but if you really need to sort on the db-level you could just use peta poco to do so. The core does not have any methods for sorting on date at them moment - But I would say that we're honting millisecounds here =D
The MailingListTreeController looks like this:
https://gist.github.com/enkelmedia/8ba9c77b2f14ef6c29578aec6c0a7961
Thanks your engagement with this =D If people find this way of sorting the newsletter good I might be something that we add as an option i future releases.
Thanks again!
is working on a reply...