Jump to content

adrian

PW-Moderators
  • Posts

    11,097
  • Joined

  • Last visited

  • Days Won

    365

Everything posted by adrian

  1. Another possibility if you are just wanting to update fields and templates (coming soon): https://processwire.com/talk/topic/2117-continuous-integration-of-field-and-template-changes/?p=68899 Are you wanting to just update their fields / templates, or page content as well? Migrator was designed primarily for page migration and the field and template component is really just part of the process if the content being migrated includes fields and templates that are not available on the destination PW site. So your users might find the workflow a little strange if they are selecting a parent page to import content to if you are just wanting update them with new field / templates. However, if you are wanting to push new page content to them as well, then this is exactly what it's for
  2. http://processwire.com/download/ ProcessWire 2.4 at GitHub View, clone, fork or download the latest ProcessWire version and/or source code at GitHub. See also the dev branch which always contains the latest updates not yet migrated to the stable version.
  3. It should work just fine. Did you remember to select your search page in the module config settings? Is your search.php file the standard one that came with PW? Are you using the version posted to the modules directory (http://modules.processwire.com/modules/process404-search/) / Github (https://github.com/adrianbj/Process404Search) or one of the older ones posted as attachments to posts in this thread? Also, what version of PW are you using? It needs to support the passing of arguments via render(), so you need 2.4
  4. Maybe someone should grab the new version of the ACE core (https://github.com/ajaxorg/ace) and add it to a Fork of Adam's module and submit a PR to him.
  5. I am seeing the same problem with the latest dev 2.4.11 - we have mentioned it to Ryan, but agreed - a comment from you on that Github issue would also be great!
  6. The last commit was Oct 9 last year and that was just a bugfix by me. https://github.com/adamkiss/InputfieldAceEditor/commits/master There is a bug in the modules directory that causes it to incorrectly report the last updated date!
  7. Sorry, I haven't had a need for it yet, but i do think it is an important improvement for PW and I know I'll want to sort something out for a long term project I am working on, but it might not be for a couple of months still.
  8. I think that is the only extra one that is built in, but not installed by default. https://processwire.com/talk/topic/3719-other-permissions-like-page-publish/?p=36446 One thing to note about it is that once it is installed, users won't be able to edit an existing published pages unless they also have page-publish permission. https://processwire.com/talk/topic/4094-publishunpublish-a-page-setting-required-to-edit-published-pages/
  9. Sorry, haven't read this thoroughly, but quick comment. To pass $useMain via render, you need to use the $options array: https://processwire.com/talk/topic/3145-multiple-views-for-templates/?p=32876
  10. I don't think it is actually added though - if you look at the field_roles database table and look for entry with a pages_id that matches the user, there won't be one. There should be one with a data: 37 (page id of the guest role). When you view the user page, there is some logic that ensures the guest role checkbox is checked, but it's not being stored in the database.
  11. What about: foreach(array('guest', 'customer') as $r) $u->addRole($r); Still, I don't see any reason to add the guest role manually, so if you are only adding one other additional role, then you probably don't need anything to reduce multiple lines. It seems like maybe something changed recently. What version of PW are you running? If I test on 2.4.5 the guest role is automatically added, but not in 2.4.11 - https://github.com/ryancramerdesign/ProcessWire/issues/588 Wow - I am having a rough morning - nothing has changed - behavior seems to be consistent through versions.
  12. Try mousing over the collapse down arrow over on the right - that does what you are looking for, or better yet, install: http://modules.processwire.com/modules/helper-field-links/
  13. Are you still trying to call $page->blog_summary; etc? If you are on the homepage, you need to define the page of the post that you want to get the content from. Perhaps this does what you need? $lastPost = $page->children->last(); echo $lastPost->blog_summary;
  14. I don't think I am missing anything here. Isn't it as simple as echo'ing $t->id ? You have t->id
  15. The table name should be: ProcessRedirects - so you should be able to just rename it using PHPMyAdmin or via SQL command line. It is created here: https://github.com/apeisa/ProcessRedirects/blob/master/ProcessRedirects.module#L326 Did you move from Windows to Linux? Names are not case sensitive on Windows, but they are on Linux? Still, not sure why it would have been created in lowercase in the first place, given the code that creates the table.
  16. https://github.com/NicoKnoll/InputfieldQuickTags
  17. Saving a site profile like Nico mentioned is a great option if you want exactly the same starting point for each site. If you want some more flexibility, there are a couple of other options. One is the new field migration tools built into the dev version of PW. There are template migration tools coming shortly. See here: https://processwire.com/talk/topic/2117-continuous-integration-of-field-and-template-changes/page-6#entry68899 The other possibility is Migrator (https://github.com/adrianbj/ProcessMigrator), which can migrate a page tree and its fields and templates (and template files). With this option you can install the default PW profile and then add in additional components as required. If you think the components are generic enough that others might find them useful, you can even contribute them to https://github.com/adrianbj/ProcessWirePageLists/ and they will be available as an automatic install directly from Migrator.
  18. Just a head's up - as of today, the dev version of PW now supports CURL if allow_url_fopen is disabled (https://github.com/ryancramerdesign/ProcessWire/commit/bbd7569de8f9b398d35e2a12226a4e34b1224bf8) so if your host supports that by default, you may not need to do any modifications to get modules downloading automatically.
  19. Yep - I did click on the module title I do think that javascript action should be removed - it confused me
  20. Maybe this could be a new third party plugin for the Migrator module (https://github.com/adrianbj/ProcessMigrator) If you haven't seen it already, the first plugin for it is Nico's MigratorWordpress (https://github.com/NicoKnoll/MigratorWordpress) which also converts XML to JSON for use with Migrator. I'd be happy to help if you have any questions on how to implement.
  21. This is what soma is talking about: https://processwire.com/talk/topic/6605-module-textarea-preview/
  22. There is also this plugin for CKEditor: http://ckeditor.com/addon/mathjax As of yesterday's PW dev version, external CKEditor plugins are supported and very easy to manage: https://github.com/ryancramerdesign/ProcessWire/commit/4b12d2e4f2ceb7eebb52261e723a847e08c8a569
  23. There is a threaded comments modification available for PW: https://processwire.com/talk/topic/2623-comments-core-reply-feature/ I haven't tried this with either of the blog options, but I would imagine it will work.
  24. You need to set outputformatting off before you save: https://processwire.com/talk/topic/490-how-to-reset-your-password-how-to-enable-the-forgot-password-function/
  25. You can use markdown. Does this help: https://processwire.com/talk/topic/1424-html-in-fileimage-descriptions/
×
×
  • Create New...