Multiple issues since last upgrade

[tpx-mk]

I recently upgraded Netbox from 4.2.x to 4.3.7 and with it the netbox-qrcode plugin from 0.17 to 0.18.

Unfortunately I have multiple issues with the new plugin version:

• Newlines (\n) in text_template are not working anymore
• font is beeing ignored (or maybe not found anymore)
• Cable terminations are empty (same as Cable QR not showing terminations #115)

Examples:

        'netbox_qrcode': {
                'font': 'Tahoma',
                'font_size': 22, # If the value is 0 or the line does not exist, then the text is automatically adjusted
                'label_height': '29mm',
                'label_width': '90mm',
                'label_qr_height': '24mm',
                'label_qr_width': '24mm',
                'label_qr_text_distance': '2mm',
               # per object options
                'device': {
                        'text_template': '{{ obj.asset_tag }}\n\n{{ obj.name }}\nS/N: {{ obj.serial }}',
                },

[mhdask]

I am not sure if the defaults have changed, but for QR codes on cables i am using the following config:

'netbox_qrcode': {
  'cable': {
    'label_height': '12mm',
    'qr_box_size': 1,
    'font_size': 12,
    'text_template': '{% for termination in obj.a_terminations %} {{ termination.device.name }} {{ termination.name }} {% endfor %}\n{% for termination in obj.b_terminations %} {{ termination.device.name }} {{ termination.name }} {% endfor %}',
},

However, my newlines does not work anymore either

[kj7ice]

v0.0.18 renders the label directly as HTML now. For text_template, I replaced my single newlines \n with HTML line breaks <br> and double newlines \n\n with HTML paragraphs <p>. The config from the original post might be updated to:

'netbox_qrcode': {
    # per object options
    'device': {
        'text_template': '{{ obj.asset_tag }}<p>{{ obj.name }}<br>S/N: {{ obj.serial }}',
    },
},

Looking at the template source (netbox_qrcode/templates/netbox_qrcode/qrcode3.html), it appears the font setting is fed directly into the CSS font-family property. It is possible that your browser does not support or recognize Tahoma, and since that was the only font specified, it fell back to something else. I think you could set a comma-separated list of font names and generics in your font setting the same as you would in CSS, but I have not tested this.

'netbox_qrcode': {
    'font': 'Tahoma, Arial, sans-serif'
},

[tpx-mk]

@mhdask :
thanks, this is working. I was trying something like this but didn't find the solution. is there a list of all {{ obj }} attributes (including nested objects) somewhere?

@kj7ice :
thank you very much. I realized the HTML interpretation myself after posting my issue here. it seems the documentation needs to be updated properly - it still claims that a simple \n newline should work and HTML is only "permitted":

also with the font issue you seem to be right, it's working as you suggested.
still, I'm not happy on this behaviour. in 0.17 and before the font was saved on the server and the text was included into the label as an image, so every print looked quite the same. I totally get it that a HTML/CSS approach is much more flexible and configurable, but the look of the label now depends heavyly on the client system and is not the same anymore regardless on whom is printing it.
is there at least a possibility of embedding the font (I'm actually not using Tahoma) into the CSS template?

[mhdask]

thanks, this is working. I was trying something like this but didn't find the solution. is there a list of all {{ obj }} attributes (including nested objects) somewhere?

{{ obj }} refers to the instance for which you are configuring the QR code text template for - In this case this would be the Cable class
dir(Cable) reveals the attributes for the Cable object:

>>> dir(Cable)
['DoesNotExist', 'Meta', 'MultipleObjectsReturned', '__class__', '__delattr__', '__dict__', '__dir__', '__doc__', '__eq__', '__firstlineno__', '__format__', '__ge__', '__getattribute__', '__getstate__', '__gt__', '__hash__', '__init__', '__init_subclass__', '__le__', '__lt__', '__module__', '__ne__', '__new__', '__reduce__', '__reduce_ex__', '__repr__', '__setattr__', '__setstate__', '__sizeof__', '__static_attributes__', '__str__', '__subclasshook__', '__weakref__', '_abs_length', '_check_column_name_clashes', '_check_composite_pk', '_check_constraints', '_check_db_table_comment', '_check_default_pk', '_check_field_name_clashes', '_check_fields', '_check_id_field', '_check_indexes', '_check_local_fields', '_check_long_column_names', '_check_m2m_through_same_relationship', '_check_managers', '_check_model', '_check_model_name_db_lookup_clashes', '_check_ordering', '_check_property_name_related_field_accessor_clashes', '_check_single_primary_key', '_check_swappable', '_check_unique_together', '_do_insert', '_do_update', '_get_FIELD_display', '_get_expr_references', '_get_field_expression_map', '_get_next_or_previous_by_FIELD', '_get_next_or_previous_in_order', '_get_pk_val', '_get_unique_checks', '_is_pk_set', '_meta', '_parse_save_params', '_perform_date_checks', '_perform_unique_checks', '_prepare_related_fields_for_save', '_save_parents', '_save_table', '_set_pk_val', '_validate_force_insert', 'a_terminations', 'adelete', 'arefresh_from_db', 'asave', 'b_terminations', 'bookmarks', 'cf', 'check', 'clean', 'clean_fields', 'clone', 'clone_fields', 'color', 'color_name', 'comments', 'created', 'custom_field_data', 'custom_fields', 'date_error_message', 'delete', 'description', 'docs_url', 'from_db', 'full_clean', 'get_absolute_url', 'get_constraints', 'get_custom_fields', 'get_custom_fields_by_group', 'get_deferred_fields', 'get_length_unit_display', 'get_status_color', 'get_status_display', 'get_type_display', 'id', 'journal_entries', 'label', 'last_updated', 'length', 'length_unit', 'objects', 'pk', 'populate_custom_field_defaults', 'prepare_database_save', 'refresh_from_db', 'save', 'save_base', 'serializable_value', 'serialize_object', 'snapshot', 'status', 'subscriptions', 'tagged_items', 'tags', 'tenant', 'tenant_id', 'terminations', 'to_objectchange', 'type', 'unique_error_message', 'validate_constraints', 'validate_unique', 'verify_mro']

To my knowledge this is the only way to learn what attributes are available for each type, and i dont think there is a way to reveal the nested attributes - You have to manually dig through them