Hello.

I've been around Drupal a looong time and this is the first module I have ever tried and have no idea how to use it or what to do with it.

Could you please explain, step by step, how to use this module. There is no README and your work interests me alot. I understand the idea behind the codes themselves, just not how your module implements them. Certainly not on the Preset stuff.

I am using the DEV version because the official release does not seem to work on 6.10 Drupal. If it does, I can't locate it.

Do I need to fiddle with the theme? I believe so, but do not know how or where with this module. How can I actually use these codes on a site? I apologize for my lack of understanding, but I need some serious handholding on this one.

Thanks,

larry

Comments

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented
Status: Active » Fixed

Hi larry,

Firstly, let me apologize for the frustration you must be feeling in not being able to figure out this module.

In the 6.x.1.x-dev build there are three ways to implement mobile codes, where as in the 6.x-1.0 version there are only two methods, however based on the information you have provided it is apparent that only two of the three methods are relevant.

Input Format:
The first method, which is available in both 6.x-1.0 and 6.x-1.x-dev, is to use an Input Format.
Being that you have been around Drupal for so long I would assume that you have run into Input Formats before, if not you can get a quick overview at: http://drupal.org/handbook/modules/filter

Simply turn on the Mobile Codes filter and use the format which is defined both in the code hints on a node creation page, or on the Mobile Codes project page: http://drupal.org/project/mobile_codes

CCK/Views formatter:
This method is only available in 6.x-1.x-dev.
Again, being around Drupal for so long I would assume you have seen CCK/Views formatters before.

To use, you will need a CCK text field for the content of the Mobile Code, and once you have created the field you will need to setup the Display for the field (/admin/content/node-type/[node-type]/display) to the Mobile Code preset you wish to use.

 

If you have any more trouble using this module, let me know.

Cheers,
Deciphered.

larry’s picture

larry commented

Hello Deciphered,

I very much appreciate your response.

You need not apologize for my ignorance of your module...although the frustration is there. I have been working with it for a bit. I don't have it yet, but I'm close. Here are some points of confusion:

I have naturally found the Input Filter. I apologize for not thinking about them. It's been a long time since I fiddled with them and the modules I normally use don't require them per se. Backlinks and Freelinking are the last two modules I used that implement the Input Filter. Sorry, that's pretty silly on my part.

Presets are not being saved. I assume they should be, but when I make one and check 'List', they're not there. I am on drupal 6.10 ( soon to be 6.11) using the dev version of mobile codes.

When I save a node, I see the filter arguements:

[mobilecode preset="preset" name="name"]content[/mobilecode] or
[mobilecode type="type" data="data type" size="size" name="name" tinyurl="tinyurl"]content[/mobilecode] -- generated as is in text, depending on what I choose

They are not getting and placing the image. I have an idea why. I don't know what goes in the 'content', that is -- content[/mobilecode]. All the other inputs are clear to me and I see that with Presets, if one is saved, the saved preset would be placed automatically -- I think. What goes there within 'content[/mobilecode]?'

Do I need to fiddle with the theme layer? I don't think so as I believe the Input Filter takes care of all of that.

Your site, theskindrop.com, is nice. I found only a few images using the mobile code images, but the point is well made. Am I correct in thinking these images are generated from Nokia? That is, a call is made to the Nokia site when an image is requested and Nokia generates it your module formats it?

If you don't mind, could you paste a 'bulletproof example' that should work, just so I can get an example up and running. If I can see that, then I can work further on my own without bugging you...

Thanks again for your response and help. This is an interesting module.

cheers,

larry

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Hi Larry,

When you updated from 6.x-1.0 to 6.x-1.x-dev did you run update.php? You should always run update.php after updating a module
There are significant changes between 6.x-1.0 and 6.x-1.x-dev and not having run update.php may account for the presets not being saved.

If you are seeing the mobile code filter you supplied as plain text it is likely that you have not properly enabled the filter, or you aren't using a input format that has the filter enabled. Make absolutely certain that you do have the filter enabled on which ever input format you are using.

Content = content.
Whatever you want the content (data) of the mobile code to be goes where the word 'content' is in the example.

No you don't need to fiddle with the theme layer at all.

The module does make a call to the nokia mobile codes service, then saves the files to your file system for future use.

If you are still unable to get the module working based on the information I have provided let me know and I will try to provide you with a step-by-step guide.

Cheers,
Deciphered.

larry’s picture

larry commented

Hello Deciphered,

Ok. I got it. Woohoo.

You were correct about the update script. Normally, Drupal gives a message. The reason why it did'nt this time is because the tables did'nt exist, so there was nothing to update. DOH!

I appreciate you getting me to the point where I can use this. This is a very cool module.

Now, if you don't mind, I'd like to pick your brain a bit about the structure of arguements. Your arguements are pretty flexible in turning information from a Drupal site into a mobile barcodes.

However, after reading through the Nokia site and much elsewhere, there are certain things I am still uncertain about.

1. How much information cam actually be stored within the Datamatrix and QR code types? I know the bigger the image, the more information. But how much is that actually? 10kb, 1M...?

2. How can I encode user profiles? Of course, I could just encode the URL but I'd like the profile information itself. Additionally, is it possible to place an image within a user profile, so when it is visited, the mobile barcode image is offered up?

3. Do you prefer Datamatrix or QR code. I ask because I've read that even though the are both non-proprietary, open standard formats, Datamatrix is more universally supported. Is that true? I see on theskindrop.com, you use QR code. Why?

4. What mobile barcode reader do you recommend? I have a cheap sony ericsson w200i that is not supported by the Nokia offerings. I looked at i-nigma and Beetag, but I'd like your opinion.

Thanks again for all the help...and the module.

cheers,

larry

deciphered’s picture

deciphered
Primary language English
Location Ballarat, Victoria, Australia
commented

Hi larry, glad to hear everything is working for you now :)

In regards to your questions, I will answer what I can:

  1. I can't really answer this, all I can do is speculate.
    Based on the fact that the nokia mobilecodes generator requests that you don't go over 60 characters, that would mean a code should only eve contain 60 bytes of data.
  2. That's an interesting question. One of the features that the nokia mobilecodes generator implemented that I have not yet implemented is the ability to create vCards, so that would certainly be an option.
    If this interests you, please create a feature request in the issue queue.
  3. I personally prefer QR codes. I believe that they are actually easier for most readers to detect as they have three points of reference. Plus, superficially they look nicer.
  4. While I don't personally have a preference for reader, when I wrote the module I was using the built-in nokia reader on the N95, which I never really had any issues with. Now I have the N96 and the built-in reader, a 3rd party reader, does not work nearly as well.
    Experiment and make your own decision.

Hope this was of some help.

Cheers,
Deciphered.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.