wdforyii Follow @yiiframework

Hi everybody, I try to use this module, but I Get this Error:

Fatal error: Call to a member function getAssetsUrl() on a non-object in ...\protected\modules\wdcalendar\controllers\DefaultController.php on line 60

Can You Help me please??

wow this is so great. i don't know great module before. this is so cool. thank you :)

hello

this is very nice extension. i want to put it on my dashboard. i search a lot but i cant find out the way how i put this wdcalendar in dashboard module..

anybdy have solution?

thanks in advance.

Hy. How can i determine what fields are required in events array? ( datafeed.php listCalendarByRange() )

Hello imehesz, congratulations for the good wdcalendar for yii implementation. It is very valuable for me!

I modified datafeed.php to use Yii::app()->user->id when adding/updating/deleting/retrieving of data. Added user_id (int) to data table.

Happy to share.

It seems the value is hard coded to 8

I replaced the value with [code] if (confirm("Are you sure to remove this event")) {
var param = [{ "name": "calendarId", value: <?php echo isset( $event ) ? $event->Id : '' ?>}]; [/code]

Hi,

The instructions for wdforyii say that "You can either embed the calendar in your own design, or leave it to display full screen (default)". As a newbie, I can't work out how to embed the calendar in a view though. Could someone advise me please?

Thanks.

Hola , para que funcione la extension se debe renombrar la carpeta a wdcalendar.Luego funcionara perfectamente. Saludos!

Da:Sourcerer,

Thank you very much for taking your time and giving me a detailed explanation. I (more or less) completely agree with you on everything.

When I originally looked around for a usable calendar for Yii, I simply could not find one. Period. They were either too slow, or they looked like they were from the 90s (which was a long time ago in computer years :) ). And fortunately/unfortunately I found this one to be OK, not perfect, but it did the job.

Obviously this is not for everybody, but if you need a modern looking calendar in about 10 minutes, there you go.

On the development side, I really don't want to change the way WD handles their internal SQL/PHP stuff (or the DB schema, column properties etc) simply because when a new release comes around (with new features, hopefully soon) I should be able to just plug-n-release. Is this the best approach? Maybe not.

In the future I might release a new extension, that uses WD only for displaying, and handle the internal stuff through Yii (with AR, permissions, table prefixes etc) but it won't happen for a while.

Oh, and if you managed to have a good Yii calendar, maybe you should release it as an extension ;)

thanks again, --iM

Well, thanks for your explanations. Still, I'm not very convinced. I'd love to provide patches but I am currently working on a payed, closed-source project for which I am writing a spanking new implementation, so that's right off.

So then, I am (and were) totally aware that you are not the person behind JQ Calendar. However, it came to my attention that you took JQ Calendar's demo code and shove it into a Yii module. This approach is very problem-laden, especially since JQC's php-code isn't exactly top-notch. Anyway, JQC is a js-library. Hence, the supplied demo-code should be neglected. Some hints:

1. Your installation process consists of creating a single table. There are way better methods than having a separate controller for just that (see CDbLogRoute and CDbHttpSession for that)
2. The table name is hardcoded. This means, there can only be a single calendar throughout an entire application. Please consider using a placeholder for that. This would also allow table names blending into existing naming conventions (e.g. erp_calendar instead of jqcalendar)
3. All SQL operations are being routed through a separate db-connection, totally bypassing Yii's existing one. This does not only add additional overhead, it also forces you to use MySQL. If you must ignore such fine features as Yii's fine concept of Active Records, at least use its query builder in order to issue (mostly) RDBMS-agnostic commands.
4. If you'd like to render partial views (suach as the edit form), use CController::renderPartial() instead of applying a new theme.
5. Please stop using die(). Yii::app()->end() is the way to go.
6. Yii provides some excellent services for dealing with values in JavaScript/JSON. Just see the CJSON and CJavaScript classes and use them.
7. More of an extra: The existing table design might be lacking a BTREE index on the StartTime field. Lookups will be much faster for larger datasets. Also, consider renaming some of the fields to something that makes more sense. xTime for a field holding a DATETIME is outright evil.
8. If you must operate on date values, try to make use of PHP's superb DateTime class. You'll find the parse-, format- and modify-functions most useful.
9. Lastly, stop being so obsessed with modules. Try putting everything in a widget, instead. Right now, if I'd want to display a calendar at more than one place, it would be close to impossible.

So, the monkey-poop thing still stands. The module might be good enough for people who just need something that works more or less out-of-the box. For everybody else, it is entirely unusable.

Da:Sourcerer,

thank you for your kind words, very nice :)

I did NOT write WD Calendar! I just ported it over so it can be used for Yii projects. It was NOT written for Yii, it was (and it IS) a stand alone PHP, JQuery calendar. So obviously it has nothing to do with templates or DB layers etc

Could it be improved? Of course it could. Just like anything else. I'd be more than happy to apply your patches, but I want to keep the code as close to the original as possible, so when a new jQuery extension arrives, I can easily update this module.

Thanks again, --iM

Were you on prescription meds while writing this module? While trying to make use of it, I might have lost a good portion of my sanity. Why on earth would you go and try to bypass everything good and/or established that comes with Yii? Such as its template engine? And its database abstraction layer? Most of the time I've spent digging through your code, I were under the impression a chimp smeared his doo-doo over a keyboard. Please fine sir, consider putting this module out of its misery, burry it in your backyard and start anew. The way it is, there is absolutely no way this could be included into a project that - once released - doesn't make pandas cry.

hello, and thank you!

Recurring events are currently not supported, but they say on their site here that it's in the works.

--iM

Hi , The module is nicely functional I would love to see a frequency (repeat feature like Google Cal) maybe it's there butI didn't see it great work