Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About Sebastian

  • Rank
    Jr. Member

Profile Information

  • Gender
  • Location
    Karlsruhe, Germany

Recent Profile Visitors

1,144 profile views
  1. I'm with @Macrura as i'm using wireRenderFile() extensively with a dedicated /views/ folder where I can organise my output in components / atoms / whatever you want to call it, using templates (and sometimes /fields/field.php) more or less as controllers. @bernhard brings up some good points I haven't thought of though, especially the JS part - I awkwardly tucked that into wire('config')->scripts, which isn't as elegant / nice. Anway, it's great having the flexibility and options to use PW as you see fit Quite liberating.
  2. Thanks bernhard for a very informative post. I do have a follow-up question though: How would i make the new panel / custom admin page accessible to a non-admin role? Currently it works great as superuser / admin using another role, logged in as a non-admin user there's only the "pages" tab, nothing else. The way I understand it, since it uses the "admin" template, I can't really manage access through template settings (?). I might overthink this though, anyone got an idea? Edit: Actually, i'm sorry, this is a duplicate of Which of course i found 2 minutes after posting the question, but not during the hour of research before..
  3. Hey adrian, what I did is export / reimport the DB and copying the files over, as per usual. I'd gladly check Process assignment wrt Blog, how do I do that? thanks, Sebastian
  4. Hi @kongondo. Well the difference is that localhost ist still PHP 5.6something and there the site runs out of a subfolder. We're going full PHP7 on servers going forward (I'm guessing that's not uncommon now), so that's maybe something worth keeping an eye on. I'm not sure if the problem is PHP 7 though - if I find the time i'm gonna setup a fresh page on 7, and install the blog module there - I'll report any findings here.
  5. I'm, having some issues after putting a site on a live server - maybe someone has an idea as to how to solve this. I moved the site from localhost/pagename to pagename.tld. The blog posts show up in the frontend, so that's fine. The issues are as follows: In the admin area, clicking on the "Blog" Tab (which links to pagename.tld/processwire/blog/) results in " The requested process does not exist " So there's no functionality there. I realize this is basically a 404 in the admin, not sure how to fix that though. I'm using PW 3.0.75 and the latest blog module version off github, PHP7 on the live server. Anyone got an idea as to how fix this?
  6. Oh wow @Nurguly Ashyrov this is an amazing effort. SO much potential usecases. Thanks for all your work. Maybe and depending how you feel about it you could mention this modue in the modules section, I only accidently kind of stumbled upon it here in Offtopic > Pub. This deserves much wider recognition.
  7. Thanks LostKobrakai. I think I tried that, but in retrospect might have only changed the collation. Going to test setting both.
  8. Hi gang, did any of you ever have to save emoji to the database (and get them out / render them later) per chanche? I'm struggling as to what's the best way to do it. Plain text fields isn't working of course, CKEditor isn't either. If anyone had a quick hint as to where to look at I would be grateful. Thanks, Sebastian ?
  9. Hi kongondo, thanks! That didn't accour to me at all. Makes a lot of sense too, I was working aroung the <button> instead of <input> for form submission already and was wondering why these elements were used insted of the more standard ones I've been working with pw for at least 3 years now (also reading the forums, registered back then etc.) but that somehow never came up. I also appreciated your work on modx extensions in the past btw! Might have a question regarding your dynamic selects module soon ;-)
  10. Hi everyone, quick question: Using the form API, is there a way to render a standards compliant <fieldset> <legend>Legend</legend> /* some input fields */ </fieldset> construct (for use in a frontend form)? Whenever I use $fieldset = $modules->get('InputfieldFieldset'); $fieldset->label = 'About You'; [add a bunch of fields, add them to the fieldset, add the fieldset to the form] not only does the fieldset get somehow mangled in divs, I also don't get a html legend element. I tried using $modules->get("InputfieldMarkup"); and construct the fieldset/legend myself, but that ends up with <div> <fieldset> <legend>Legend</legend> </div> I searched the forum, but only found some similar questions and no real answer (unless I missed it, which is entirely possible )
  • Create New...