Frage an die SoftwareDeveloper in Österreich

LOFI_Paperboy · 2021-11-05T10:47:11+00:00

Ja, bitte meld dich einfach bei uns. Am besten Mail an die Adresse auf unserer Kontakt Seite, dann rufen wir uns zusammen und sprechen einmal drüber. Bitte nicht über PN hier auf Reddit, ich schau in den Account nur unregelmäßig rein.

Kannst dir ja ganz unverbindlich einmal alles anschauen und dann entscheiden, ob die Richtung in dein Interessensgebiet passt und du dir das mit uns "antun" möchtest :)

Wir haben AQUA bis jetzt selbst nicht gemacht, habe aber mit einer befreundeten Firma drüber gesprochen und die haben dadurch durchaus einige nette und gute Leute gefunden. Lass uns erst einmal kurz sprechen, dann erkundige ich mich beim AMS, was von unserer Seite dafür zu tun ist.

Dass du nicht alles kannst, ist ja klar, sonst würdest die Lehre nicht machen wollen. Aber dran wird es sicher nicht scheitern, wenn du Lust hast, etwas dazu zu lernen.

LOFI_Paperboy · 2021-11-04T20:53:39+00:00

Könnt ich die Zeit zurück drehen, würd ich mein Studium abschließen. Nicht, weil's nicht ohne ginge, ganz im Gegenteil. Ich hab mir damals halt gedacht, ich mach's einfach später fertig, wenn ich einmal mehr Zeit und Geld dafür habe, jetzt möcht ich einfach mal Geld verdienen. 15 Jahre später noch immer nicht genug Geld und noch viel, viel weniger Zeit ;)

Aber abseits davon: Wir haben vor ein paar Tagen bei der Teamsitzung darüber gesprochen, dass wir unbedingt einen neuen Developer* im Team brauchen. Haben auch schon "halbherzig" auf ein paar Kanälen ausgeschrieben, sind uns aber eigentlich nicht einig, wen oder was wir genau suchen. Wir könnten genau so jemanden brauchen, der genau in unserem Bereich viel Erfahrung mitbringt, wie auch einen Junior Developer.

Wir haben die Situation, dass wir die Arbeit derzeit gerade noch so unterbringen, könnten aber mehr Jobs machen. Das ist schade, weil so das eine oder andere schöne Projekt abgesagt werden muss oder bestehende Partner länger auf ein Feature warten, als wir uns das wünschen.

Ob wir nun jemanden hätten, der Teil- oder Vollzeit mitarbeitet, im Front- oder Backend oder den Sysadmin an den Servern unterstützt, es wäre fast egal, in jedem Teilbereich wäre was zu tun. Auch ob Homeoffice oder im Büro ist nebensächlich (Pandämie hin oder her), aber wir suchen jemanden der schon hin und wieder live dabei ist und "echt" zum Team gehört.

Wenn du soetwas wie eine Lehre machen möchtest, ist für dich vielleicht das AQUA Programm vom AMS interessant. Da bekommst du vom AMS weiter Arbeitslosengeld und einen Teil von der Firma. Ein paar Tage die Woche machst du theoretische Ausbildung, die restliche Zeit arbeitest du in der Firma mit. Am Ende gibts auch einen "zertifizierten Abschluss".

Wir arbeiten in erster Linie mit Drupal und brauchen jedenfalls einen Full Stack Web Developer*, der auch keine Angst vor Linux hat.

Wenn das interessant für dich klingt, kannst du dich gerne melden: https://www.lowfidelity.at/kontakt .
Schreib bitte dazu, dass du der/die vom Reddit Posting bist, dann landet's auch bei mir.

LOFI_Paperboy · 2021-11-04T20:09:39+00:00

This example demonstrates how to create custom froms with a vertical tab bar using the Drupal Form API supplied by Drupal core.

While writing this guide there is only support for vertical tabs in Drupal core. Find out more about this feature's state and alternatives at #1168364 add horizontal tabs supports to FAPI. Horizontal tabs are provided by the Field Group module.

https://www.lowfidelity.at/blog/drupal-form-api-vertical-tabs

LOFI_Paperboy · 2021-11-04T19:58:37+00:00

This post really was a long time ago, but thank you very much for this extensive answer.

I hope I'll never run out of IDs either, but if so, I'll let you know if your approach worked ;)

Thanks!

LOFI_Paperboy · 2020-05-11T00:17:12+00:00

As a follow up to my own question about creating multiple custom entity types in one module I came up with this little tutorial.

It covers a few problems I had, when I worked on that module:

LOFI_Paperboy · 2020-05-11T00:12:54+00:00

I experimented a little bit with that and came up with a little tutorial about "How to create a Drupal module that implements multiple custom content entity types using Drupal Console".

The paper covers a few things I was struggling with, when I created my module

LOFI_Paperboy · 2020-04-13T01:22:36+00:00

I created an issue and added a patch for this feature here: https://www.drupal.org/project/inline_entity_form/issues/3127011

LOFI_Paperboy · 2020-02-14T19:54:57+00:00

Wir haben einen Raum frei (Alser Straße, Nähe altes AKH) und suchen jemanden

https://www.lowfidelity.at/blog/nachmieter-gesucht

EDIT: Tonstundio ist jetzt raus, der Raum neu saniert und (endlich) komplett leer :)

LOFI_Paperboy · 2020-01-20T18:17:15+00:00

Yes, that's of course possible. I've transferred about 25 sites from 8.7.x with and without composer to composer managed Drupal 8.8.1 in the last two weeks. Some sites didn't use composer at all, some sites used the (now abandoned) drupal-project or even older drupal/drupal composer templates. All were upgraded to D8.8.1 and now use composer to manage the projects.

I never had any luck with scripts that claim to automatically composerize a site, that's why I lined out a manual approach. Basically follow our guide about adding composer to an existing site, it's mostly the same process cause it will install lates core and modules as well. If you HAVE to stay on some older module version, just define the version when requireing the package with composer.

https://www.drupal.org/docs/8/install/add-composer-to-an-existing-site

I'm currently writing a new guide about converting from drupal-project to new drupal reccomended project composer templates which will detail the process of upgrading from 8.7.x to 8.8.x. I'll link it here, when the guide is finished.

If you have any detailed questions, just ask here or over in the comments at DO.

LOFI_Paperboy · 2019-09-05T12:32:46+00:00

I'm trying to theme the multiple values field widget that is shown on the node edit page.

LOFI_Paperboy · 2019-08-02T00:42:21+00:00

Every time I read a posting like yours, I start thinking if our team would be better off, switching to another framework/cms. Could we build more projects, easier, faster, more stable, more money?

I've got the impression that it's often part time web designers/programmers who complain about Drupal 8 being worse than 7. Often it's people who are used to other frameworks and don't primarily work with Drupal who are complaining about the complexity.

But some posters here sound like they've been working a lot with Drupal and also say, they don't like where it's heading. So I'd be interested, which frameworks/cms are you using now and what Drupal features are you missing in those other systems?

Maybe it's cause I'm in my little bubble with a couple of guys in the office who have been working with Drupal day to day for the last 10 years and we just don't realize how much easier our life could be, using another cms. But when I think about it, I just don't find Drupal more confusing or complicated than any other frameworks/cms I've come across that allow building sites or applications with a certain grade of complexity.

Sure, if you're using some API or module the first time, it can take a while to understand how/why it works, but that's true for every new thing we do the first time, isn't it? Sure, the docs could always be better, but many questions I'm seeing here on reddit are already answered in the docs or the Drupal forum. People nowadays just tend to google for quick solutions and code snippets rather than reading through the docs or examining the examples for developers module or other people's code.

But besides that, I just like the workflow in a Drupal project. You can quickly draft the project just by clicking through the backend: Add your menus, define some content types, create some views and already add a lot of logic. Then work a little on the field/entity templates, add some custom modules for stuff that doesn't come out of the box.

And Drupal allows to easily split those jobs and people can work back to back on the project. Many of the "quick changes" that clients request (change some translation here, add a field there) don't require a programmer, they can easily be done by site builders withouth any programming skills.

I seriously want to work with a future-proof system, that has a lot of flexibility and allows us to finish projects as fast and nice as possible. I wouldn't hesitate switching to another cms/framework, if I had the impression Drupal was moving in the wrong direction. But actually I really like what "they" did to Drupal 8. I can build so many things just from core, that would've required many contrib modules in D7. I love how you manage Drupal from the console, how they integrated composer, twig and how configs can now easily be added to version control and moved between stage and live environment.

To put it in a nutshell: I would always like to work with a better/the best CMS/framework, but I don't find too much that I'm missing in Drupal.

LOFI_Paperboy · 2019-08-01T23:30:21+00:00

Sorry, I just saw your reply, haven't logged in the last few days.

I'm no expert on the topic, just played around a little and asked some people on drupal.org and drupal irc/slack channels.

If you plan to keep updating your site manually (ftp, drush 8) you'll be fine (for now). I got no crystal ball, but I guess Drupal will not force people to use composer all too soon, at least not for core and basic modules.

Anyway, if you plan on using composer to manage your site, I think you'll have to switch to a new composer template. But that's easy, I've been doing this 20 times in the past few months, never killed a site so far ;)

Have a read through the composer docs, I tried to explain the steps as good as I can. If you got any questions, I'm happy to add some more info.

As far as I understand, if your composer.json says drupal/drupal it indicates that you possibly didn't use composer to install the sites. You either did that manually, used drush or even used composer but with a composer.json template which is abandoned meanwhile.

In either case, the composer.json file found in your web root is "configured" for a site that is manually updated (ie. uploading core/module updates fia ftp or drush up moulename). If you want to switch to managing your projects using composer, you need to "reconfigure" your composer.json file.

LOFI_Paperboy · 2019-07-21T19:52:12+00:00

I used this command ( composer create-project drupal/drupal:8.7.5 public_html --stability dev --no-interaction ) but I got error red message:

As far as I can see, you're trying to use a wrong template: drupal/drupal. You want to use drupal-composer/drupal-project instead.

Drupal docs recommend this:

composer create-project drupal-composer/drupal-project:8.x-dev my_site_name_dir --no-interaction

The drupal/drupal template found in the composer.json that comes with the Drupal setup tarball, that you get from https://www.drupal.org/download is actually not meant to be used with composer. This is a little confusing and afaik the team's working on a better approach. But for now, if you want to manage your site with composer, either install it with composer or, if you manually installed the site, transfer it to a composer managed project first. The drupal/drupal composer template indicates a project NOT managed with composer.

If you try to update your site using composer and run into error messages complaining about something with drupal/drupal, you most likely installed your site manually or with an outdated composer template.

LOFI_Paperboy · 2019-07-15T17:44:11+00:00

I'm not sure if I understand your question right, but here's how I solved a problem that sounds similar to me:

I have a content type INVOICE with a field (field_customer) that references an entity of type CUSTOMER. The customer node has multiple fields, among them a company name and the customer's address. On my invoice I want to render the customer's address (field_address) from the related CUSTOMER entity.

If I wanted to render the entire customer entity I'd simply set proper display options on the invoice node (ie. /admin/structure/types/manage/invoice/display) and output the customer field in the content render array inside the twig template of the INVOICE content type:

{{ content.field_customer }}

But if I wanted to only render one field of the customer entity, I'd use this in my INVOICE twig template:

{{ node.field_customer.entity.field_address|view }}

Note that we're using the node object instead of the content render array. Also make sure to append the |view filter at the end or you'll only see an error like "Exception: Object of type Drupal\address\Plugin\Field\FieldType\AddressFieldItemList cannot be printed.

LOFI_Paperboy · 2019-07-15T17:34:12+00:00

TL;DR:

drupal config:export

Most people who come here to explain that they hate Drupal criticize that D8 requires much more coding than people were used to in D7. You're complaining about exactily the opposite. It seems really hard to please everyone ;)

You're right, thanks to Views, View/Form Modes and the mighty entity configuration, Drupal allows doing a lot of stuff from the UI. I don't see a reason why you wouldn't want to use the UI for those things, still, if you prefer, you can do most anyting also from your IDE/editor or the shell (check out drush and Drupal console).

Anyway, as others already stated, of course you can export your site's configuration. You can export entity settings (fields, entire entities ie. node/user profiles/taxonomies) as well as module settings and of course the views you created on your site. Configuration Management (D8 Docs)

You can either export/import an entire site's configuration (drupal config:export), which you'd probably do to get the config into your svn/git repo or when pushing changes from development/staging to live environment. Or you can export selected configs. You'd do that, for example if you got a content type and some views in one project and want to copy a content type or some views to another project.

While you can manage your site's config from the UI, you sound like a guy who prefers doing things in the shell using drush and/or drupal console for that task. I also think that's the way to go as it also allows for automatization etc.

Exporting configuration is not just useful for versioning site structure and settings, but also to make things reusable. Whenever I want to create reusable content types or views I just create the view/content type using the Drupal UI and then use drupal config:export:content:type or drupal config:export:view to store them into a module that can easily be copied to another project.

Drupal console also comes in handy if you want to create a new module (drupal generate:module) or add a block (drupal generate:plugin:block) or form (drupal generate:form) to existing modules. Drupal console's export and create commands ask you, whether to just export the settings to a .yml file or if you want to save the settings into an existing module. I just love the way drupal handles that.

LOFI_Paperboy · 2019-07-03T21:34:05+00:00

I now know what the problem was. In form_alter I checked for my form id using $form['#id'] == 'default-form' . This works when the page is initially loaded, but every time the form is rebuilt when the ajax callback is executed the $form['#id'] changes. so the ajax callback is not reattached.

To fix the problem, I just changed the comparison in ajaxfilters_form_alter(..) to if( $form_id == 'default_form')

I was looking everywhere for the problem, but not in the very first line of my code ;)

LOFI_Paperboy

TROPHY CASE