Jump to content

adamspruijt

Members
  • Posts

    155
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by adamspruijt

  1. I had the same issue with autocomplete not giving results, it appears to happen only when the input it place in a FieldsetTab (for me at least). Also, the input was not receiving the "ui-autocomplete-input" class when in the FieldsetTab, so from there I assume jqueryUI is not able to find the field.
  2. Hey adamkiss, I haven't seen this problem before, though I only ever use PW 2.3 (dev) and I have changed the compatibility to just list 2.3 on the theme directory. I brought the code for the field focus over from the default theme (main.js) for 2.3, it seems I removed it at some point, maybe I was having this issue. Anyway, thanks for the heads up, hopefully this fixes things for you.
  3. Love this, I had tried my hand at a very minimal theme, but it never felt right, yours looks much better than mine. Looking forward to it!
  4. When you say totally compatible, are you saying I shouldn't need to use a cookie, or that the cookie itself will work?
  5. Is multi-language support a possibility with this? I suppose more specifically "domain/subdomain" based language support, or maybe an easy way to bypass procache for all but the default language...? Hmmmn. Wait... I can use a cookie.... duh. Thanks self! (Though I'd love to hear about a better method)
  6. I think maybe this is a matter of being on PW 2.2.9? No? I can look to see if the problem is my doing, I've been building primarily on the DEV branch so I would never have seen this error. Thanks Raydale
  7. Great thanks for that, I don't use the time option on the date field often, I think when I get home I'm going to make a big FAT processwire install with everything enabled. I put together a quick fix for now, will improve later, but it is certainly usable for now.
  8. adamspruijt

    other CMSs

    LOVING The Secretary Diogo, very cool, I will have to play with this more very soon. Lots of interesting features already. Thanks.
  9. adamspruijt

    other CMSs

    I'm a big fan of Symphony CMS, before coming to ProcessWire this was my muse. There are still many things I greatly admire about the project, one of which is their BEAUTIFUL extensions site.
  10. The only special characters that are not sanitized are dashes and underscores. Not only that but, that would look like a horrible mess wouldn't it? Also there needs to be a method to determine which separator get skipped, so that the system can determine whether to append or prepend the "label". Inevitably using brackets would only have the effect of seeming more like "natural language", but the technique would still be rather complex. Either way this isn't a client facing feature, so I decided working within the constraints made more sense than overriding too much of the default behaviour of processwire. Also: UPDATE 1.0.4 - image subfields are no longer processed into thumbnails, so you can properly output the image height, width, filename, filesize etc at text.
  11. UPDATE 1.0.2 : Big improvements to Internet Explorer compatibility.
  12. For sure, that was how I had originally planned this Module, something like: fieldname fieldname {Label} fieldname {Label} problem is that all type of brackets get sanitized, I suppose that there could be a way around this but I feel the implication of playing with the input sanitization could be much more complex than the solution I've gone with.
  13. Hey nikola, from what I tested this only happens when the subfield for the "CropImage" field has not been defined and seems to be consistent with the behaviour of Soma's PageListImageLabels where I snagged the code. I added a condition to only attempt to get the thumbnail if a subfield has been provided, so now if none is provided the Module will fall back to using the source image file for the CropImage fieldtype. ALSO: Updated the Module to have joining support. Example if you want something like: 260 x 420 you would use "fieldname -x- fieldname" (or "fieldname --x-- fieldname" if you dont want the spaces) I hope that makes sense
  14. Soma! Dude... I love this, I was just pondering the other day if this would be possible, and now, done and done. So easy and fun to test ALL the admin themes now. Thanks!
  15. Thanks Ryan, sorry I forgot to post those, was in a bit of a rush.
  16. I simplified the options as a matter of personal preference, not because I thought you had too many, I can see the pros/cons of either approach, also the name "Better" is only in reference to the original implementation, though maybe a word like "Configurable" or "Advanced" would be a better choice. Thanks nikola, I will take a look at this, I don't use the thumbnail module on all my projects so I will test it with one ASAP and fix.
  17. So with all the love I have for ProcessWire page labels have always been a little less awesome than I hoped. Say like in the Skyscrapers profile you want to show the height of the tower along side the tower name, the output will end up something like: Cool Tower Name, 780 To me this just isn't good enough and doesn't always offer a lot of value to the end-user/client, so I made "PageListBetterLabels". Which gives you the power to output something like this: That there is done with this (as the setting for "List of fields to display in the admin page list" setting under advanced): images title height --ft -tall floors -floors Opened- In- the- year- year How it works anything that starts or ends with a dash does not get processed as a page field anything with the dash(s) at the beginning gets appended to the field before it anything with the dash(s) at the end gets prepended to the field after it (I hope this makes sense) one dash means leave a space, two means don't I used Soma's PageListImageLabel module as a starting point for supporting Image labels in this module, so a big thanks goes out to him and his wonderful work (I simplified the options in my implementation, to get things up and running). I mostly added this feature as I assumed the two would not work together, I may be wrong though. I will add this to the modules directory, right now I need to pick up my Wife from work. DOWNLOAD
  18. My second Admin Theme! Wow! I went for a more "App-like" style this time, I find this type of design can help a great deal with usability and some clients just really prefer it. Now the important part, screenshots! THEME - DOWNLOAD Login Page List Edit Page Page Item Move I've also attached a custom theme for TinyMCE install: compliance.zip copy to {your_site}/wire/modules/Inputfield/InputfieldTinyMCE/tinymce-3.4.7/themes/advanced/skins change the "skin" setting in {your_site}/wire/modules/Inputfield/InputfieldTinyMCE/InputfieldTinyMCE.js from "o2k7" to "compliance" ALSO put together an AdminBar mod to match, that include a search field to search entries on the back end, just because I wanted to see how that would feel. AdminBar.zip THEME - DOWNLOAD UPDATE 1.0.1 - Pushed some fixes for modal styling UPDATE 1.0.2 - Big improvements to Internet Explorer compatibility. NOTE: Relies heavily on CSS3, only tested in Chrome so far. Will be updating frequently will new feature and fixes, I just couldn't wait any longer to release it!
  19. Just pushed an update to maintain event bind in the "type to search" result. Didn't realize these were needed for installing module.
  20. Man, you guys are awesome, thanks a lot. I thought the DB route made more sense and your words on the matter really make me feel a lot better about going ahead with the changes (which in ProcessWire will really only take a few minutes ). THANKS!
  21. I am developing an ad managing/tracking tool for my employer, and the ads will be used on our main site, getting from 5-10,000 hits a day the ad view count sky rockets quickly. My current approach was to have the "stats" (clicks and views) be children of the ad they are associated with, but this would mean after a few months an ad could easily have hundreds of thousands of child entries and after a year millions. I thought maybe in this situation I could do periodic "exports" where I would dump the old data into some type of flat file that would allow client to view their advertising stats on a month by month basis, but I feel like this is prone to error... (it could also detract from the functionality quite a bit). Then I thought maybe a separate database table and use of the Processire $db class..? But in this case I wasn't sure if this was necessary (not having access to the lovely pageArray methods might not be so fun) or if there were any extra security concerns in this type of setup. I hope this explains the issues I'm facing.
  22. Great, thanks Ryan, I'm sure there will be many great concepts worth adopting in this profile. I'll have to take a look ASAP!
  23. Thanks Apeisa! It's not as though from anything I've read there is a problem with removing the attributes I just feel that it's a lot nicer to use a simple piece of css and avoid the troubles all together.
×
×
  • Create New...