Can't add nor modify a Mobile Code block

I too am unable to create a new block. It lets me fill out the add block form, but when submitted it does nothing but return back to the add block form that has the info in it that I filled-in. So, it's not working.

I'm going to try disabling, uninstalling and the re-enabling to see if that changes anything.

Disabling, uninstalling, and re-enabling didn't work to fix anything. I can't save any changes to the current_url block, nor can I Add Block. The forms appear to save but nothing is actually saved nor is there any alert/notice that anything was created/saved. This severely limits the module.

Drupal 7.27

I am now able to get the default current_url block to work (produce and present a QR Code).

I am experiencing the same thing. In addition while I can clone or even edit, it will not allow me to save any changes.

exactly same behaviour here. I can't even see the default current_url block in my blocks list.

Remove

/*function mobile_codes_blocks_export_ui_form_submit(&$form, &$form_state) {
  $form_state['rebuild'] = TRUE;
}

from plugins/export_ui files.

Plazik, I tried your suggestion and it still didn't let me create a new Preset. I did run update.php and cleared cache. This module isn't really any good unless you're just wanting a qr code for the current URL at the default 180x180 size, nothing else works to allow customization. Needs some lovin'.

I haven't tested it but it should work.

Patch #8 fixes the issue for me.

Any chances to get this into the stable version?

I can confirm that patch #8 works correctly with the latest stable version 7.x-2.1

+1 rtbc

@alibama,

+1 does nothing. If you are saying that you've reviewed the patch, both reading through the code and secondly ensuring that the patch doesn't break any of the modules functionality, then change the status of the issue to RTBC. "+1 rtbc" essentially tells me that you wan't this to be ready and committed but don't want to take on the responsibility of saying that it is ready yourself, and while I understand that entirely, someone has to take on the responsibility.

MC is not currently at the top of my priority list, but I will try to look at the issue queue as soon as I have time.

As Deciphered has asked for a little more feedback so I'll give it a bash.

Patch tackles all three areas this issue occurs, also through manual testing initially through heavy use and then minor use over the course of a couple of months I've not encountered any undesirable knock-on consequences.

Module went from unusable to very useful, I'm actually tempted to mark this as critical as the module doesn't actually function until this patch has been applied. But clearly it must have worked fine at some point so perhaps it's only an issue with newer PHP version? Not really sure, however based on the above I'm going to RTBC.