Over the past couple of weeks, we've been working with Umbraco. A couple of questions that we are uncertain about is described below.
1. Whenever we (re)publish a page, or the website has not been visited for a while, it's as thou' recompiling takes a while. Is there anyway this process can be speeded up?
2. Is the member section of Umbraco good enough to be used with around 1.000 members?
3. Let's say I want a checkbox member-property to send out an e-mail, when checked. How would one go about doing so? Making my own data type and tying it to a macro?
1. Republishing a page doesn't recompile anything, only refreshes the published xml being kept in memory. Also, all macro's that have been cached will be invalidated, so first startup of pages may be slower than second and consecutive requests of the same page.
2. shouldn't be an issue at all
3. Do you want the mail to be sent out when saving the member's details (including the checkbox). In that case, a new datatype seems a bit of overkill, could rather go with event handler that subscribes to the Save or New event and send out mail based on member property info. Actually, creating a new datatype that will send e-mail on checking the checkbox may be undesired behaviour in case you clicked that checkbox by accident (yeah, we know it won't happen to us as developers, but editor will click...)
Questions about recompiling speed, members and custom "triggers"
Hi.
Over the past couple of weeks, we've been working with Umbraco. A couple of questions that we are uncertain about is described below.
1. Whenever we (re)publish a page, or the website has not been visited for a while, it's as thou' recompiling takes a while. Is there anyway this process can be speeded up?
2. Is the member section of Umbraco good enough to be used with around 1.000 members?
3. Let's say I want a checkbox member-property to send out an e-mail, when checked. How would one go about doing so? Making my own data type and tying it to a macro?
1. That's because the Application Pool shuts down after a period of time (20 minutes), you can (not recommended - http://www.velocityreviews.com/forums/t97701-application-pool-worker-process-idle-timeout.html) change that: http://technet.microsoft.com/en-us/library/cc771956%28WS.10%29.aspx
2. Sure :)
3. Yes, create a new data type
And some more background info:
1. Republishing a page doesn't recompile anything, only refreshes the published xml being kept in memory. Also, all macro's that have been cached will be invalidated, so first startup of pages may be slower than second and consecutive requests of the same page.
2. shouldn't be an issue at all
3. Do you want the mail to be sent out when saving the member's details (including the checkbox). In that case, a new datatype seems a bit of overkill, could rather go with event handler that subscribes to the Save or New event and send out mail based on member property info. Actually, creating a new datatype that will send e-mail on checking the checkbox may be undesired behaviour in case you clicked that checkbox by accident (yeah, we know it won't happen to us as developers, but editor will click...)
Cheers,
/Dirk
Thanks guys!
is working on a reply...