Jump to content

Martijn Geerts

PW-Moderators
  • Posts

    2,769
  • Joined

  • Last visited

  • Days Won

    31

Everything posted by Martijn Geerts

  1. For "simple" websites I use usually with a 3 column design. First column is for widgets (pages stored in /widgets/ ) with a checkbox to select it's left postion and a template where to render. I can put as many pages in the widgets folder as I wish. All left widgets wil show up on the left side of the page sorted on the drag'n'drop order if it have the right template. If there are no widgets to render, the pixel space is given back to the center column. On every page I can check a widget to disable rendering. The second column is for the main content. The third column acts the same as the first. But then for the right column. Every widget is aware of $page. So I can use widgets for "photoalbums", link to siblings, children or just to show social media urls etc etc. Maybe you can have a look at delegate profile. ( the widget system included ) Ps, Documentation doesn't belong to that version anymore. So ignore it (yeah I'm lazy) For CSS framework I used Gumbyframework. Maybe this will help you out simplifying your templates.
  2. Lot of questions no answers: Where you need the repeater for ? And why not percentage ? Should there be a max on images on 1 row? Or always 4 next to each other for example?
  3. Settings You can store in the admin. (/processwire/ if you create a structure like this: /Processwire/Settings/ <- hide from menu & enable guest access ( will show open lock ) /Settings/color/ /color/red/ /color/blue/ /color/green/ /Settings/position/ /position/top/ /position/left/ /position/right/ Then the editors won't see anything in the tree. And you can query for your color or position.
  4. basic-page.php _______________________________ 01|<?php | 02|include("./inc/variables.php");| 03|include("./inc/func.php"); | 04| | 05|$content = "PHP VooDoo Magic"; | 06| | 07| | 08|include("./inc/out.php"); | 09|_______________________________| ./inc/out.php _______________________________ 01|<!DOCTYPE html> | 02|<html> | 03| | 04|<?= $content ?> | 05| | 06| | 07| | 08| | 09|_______________________________|
  5. No problems here, these days. Once in a while I experience DNS issues with process.com. (Then I switch to IP)
  6. ProcessWire gives me the old Apple feeling back. ( talking about 10/15 years ago) But we have our own Steve Jobs! Ryan Cramer has the vision, the knowhow and the social aspect we all adore. I love the things that are not in the admin, and how to handle all those other aspects. (api) I don't want a assets manager ( if there's no reference ) I don't want endless settings on a shared place. I don't want to explain ( in tutorial ) how a site works. I don't want to use some kind of TPL language inserting logic in a textfield. I don't want a headache to get data. All the above I can easily build/do with ProcessWire, the fact that I can I really love.
  7. Yep, tnx just satisfied a customer today with your fixes !
  8. Thank you Roope !!! Gonna try tomorrow if your fix will fix my issue! Parse Error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM (line 273 of ......./wire/core/Modules.php) possible solution from Roope Lookin' in dev branche now. I see Ryan has made these "fixes" 6 hours ago. Thank you very much Ryan & Roope ! I couldn't wait till tomorrow to see if it was fixing the issue. So I tried and it did.
  9. The context in your case is "mytemplate" as I understand correctly. Because multiple templates can share 1 fieldgroup.
  10. Yep followed Ryan's instructions about the modules cache. And usually I delete caches & sessions to. Here, I gonna move the development of this site to a server with a newer PHP version. So for me this problem is solved now. But open to test if Ryan needs more information.
  11. Think you're right about it. Sounds to me there's something wrong with the PHP cleaning process. As Sessions should be cleared by the server so far I know. What is the PHP version & PW version ?
  12. Yep, also deleted sessions.
  13. I'm trying to update PW2.3 to PW2.3.3. But getting error: Parse Error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM (line 273 of ......./wire/core/Modules.php) The version of PHP on the server. 5.2.17. (I know this is old, but hard to update & still higher then the 5.2.4) If I look at the source, there nothing weird about the double colon.
  14. It looks like that you need a path, not a url. (didn't test it) See checkDiskfile methode on line 1569
  15. Think your new styles will do, but there are more options. Maybe the clearfix way is more robust, when I think about it. You can do it with the clearfix way from Nicolas Gallagher. .Inputfields > .Inputfield > .ui-widget-content { /* the Inputfield's content, padded from the borders */ padding: 1em; } /* clearfix way, ps, don't need the IE7 zoom as PW doesn't allow IE7 in admin */ .Inputfields > .Inputfield > .ui-widget-content:before, .Inputfields > .Inputfield > .ui-widget-content:after { content:""; display:table; } .Inputfields > .Inputfield > .ui-widget-content:after { clear:both; }
  16. ProcessWire Productivity App QuickSilver Getting things done QUICK Sequel Pro The easiest way to handle local databases Little Ipsum Never outta reach. Sip Live's so colorfull....
  17. Lookin' great so far. And about the coding & talkin: I like it that way, PLEASE stay talkin' on the forums too. (and Wanze coding !) When Joss returns, we have a whole Social Media Platform going on right here. Think this module gonna get really useful for lot's of things.
  18. .ui-widget-content needs to calculate it's height, the css overflow property can solve it. Welcome Pauline !
  19. if "Maximum files allowed" was set to 1, the module was not able to get the image. (ADMIN > SETUP > FIELDS > imagefield ) Latest update fixed this bug.
  20. The errors (notices) tell me that the wrapper couldn't split up in two parts. The wrapper should have a double pipe || to split. Can you tell me more about the problem. - Version of PW, - Is it a single or multiimage field. - etc. (Textformatters order is important thing as one formats the other. )
  21. Totally agree with the point about the box collapse. (Ryan Help!, see Soma's post before this one "ui-widget-content") And oops, you you're right about toString my mind's a floating int string...
  22. Plugin needed the color as string not as int. Was fixed with parseInt. Update also prevent box collapse on the container. I'm not to happy about the transp as name for transparent.
  23. 01. & 02. It's /site/templates/ ( the place where to put the MarkupCSScompress.php, it's just a PW template ) 03. CSS files have to be PW accessible. ( CSS files from other sources won't work, other domains for example.) 04. The order is the order that files are in the array. 05. The module here is triggered, and uses the MarkupCSScompress.php (template) to output the combined styles.
  24. ProcessWire Logo's Michael van Laar
  25. @ceberlin Lots of modules only get activated if you want. Other modules have an early escape. (See textformatter example from Teppo's site). Then lots of modules use hooks (so you don't need duplication in your templates & it is portable). And then there are modules like ImportPagesCSV that is needed only once most of the time. After use, just de-install them. If you use modules wise, I don't see to much drawbacks from using them.
×
×
  • Create New...