Jump to content

justb3a

Members
  • Posts

    321
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by justb3a

  1. Hi, I did just a short look at the instagram api and both implemented endpoints seem to submit a media-id inside the returned array. If this is not the right one, if have no idea as well { "data": [{ "comments": { "count": 0 }, ... "type": "image", "id": "22721881", ... }] }
  2. Thanks for this module, it works even as expected in a 3.x ProcessWire installation. But it took me a while to understand how this module works and what I have to set up. At the end it's pretty easy but I had to read 9 forum pages and failed initially by installing the wrong module. I summarized all collected information and updated the Readme file (see PR at Github), maybe someone else could benefit from this. To prevent others from installing the old module as well, could @apeisa or someone else having access rights maybe add a litte note to the first post? One more thing: I use MarkupSEO and got some trouble overriding the module config data for each site. Unfortunately I found no way to hook into that specific function and decided to submit a PR as well. Now I can use the following config: $config->MultisiteDomains = array( 'domain1.com' => array( 'root' => 'www.domain1.com' ), 'domain2.com' => array( 'root' => 'www.domain2.com', 'http404' => 1932, 'markupSEO' => array( 'piwikAnalyticsIDSite' => 12, 'titleFormat' => '{title}' ) ) );
  3. I'm in the process of getting wireshell PW3 ready. But I think it could use a bit more testing before I'll finally push it into the master branch. So I started a RC branch just for this purpose. If someone wanted to try and test it – which I would really appreciate: here you go (or: checkout branch feature/devns) !
  4. Hi, here is a working example of one of my latest projects on how to use more than one contact form on a single page (PW 2.x): $optionsContact = array( 'submitName' => 'submit-contact', 'templateName' => 'estate-contact-request' ); echo $modules->get('SimpleContactForm')->render($optionsContact); $optionsRecommend = array( 'allFields'=> $allFields, 'requiredFields' => $allFields, 'submitName' => 'submit-recommend', 'templateName' => 'estate-recommend', 'emailSubject' => 'xxx', 'emailMessage' => $emailMessage, 'successMessage'=> $successMessage ); echo $modules->get('SimpleContactForm')->render($optionsRecommend); You can override every option from the module settings,. If you skip an option, the one from module settings will be used. So you don't have to pass any option to the first render call. Then you need to adapt the JavaScript to trigger the related form. If you pass another template you have to create it manually (by copying the generated one and then adapted it to the special needs, make sure to change the submitName). If an error occurs, please let me know, what the error message is and when it appears (rendering the form, submitting the form, using ajax...). I noticed already that this wasn't the best idea and changed this behaviour in the devns branch (PW 3.0.x compatibility). Unfortunately there is no way to achieve the same in the "old" version working with PW below 3.x.
  5. Hi @Piqsel, thanks for the feedback. I just installed a fresh PW 3.0.14 installation, downloaded SimpleContactForm branch feature/devns, filled in module settings. Then I added echo $modules->get('SimpleContactForm')->render(); to home.php. But I can't reproduce the message you received. Everything works as expected. Do you include the module call inside _main.php? Because the error notice refers to line 82 of /site/templates/_main.php and not to /site/modules/SimpleContactForm/xxx. Furthermore the module call doesn't include a property request. Apart from this you said the module seems to work, so maybe this error notice isn't related? Could you please try to restrict the issue by debugging the parts one after the other? [var_dump($modules); var_dump($modules->get('SimpleContactForm'));] You have to find out which part produces the error message.
  6. Got two via @webgefrickel (just in case you want one) https://t.co/o9yhWNAYVl

  7. Nope. This module uses the built-in WireCache functionality which defines the following caching periods: const expireNow = 0; const expireHourly = 3600; const expireDaily = 86400; const expireWeekly = 604800; const expireMonthly = 2419200; This isn't possible, this module just uses the existing instagram endpoints.
  8. Your ProcessWire version is not new enough. setAndSave was introduced with version 2.6.9, this was one of the reasons why I set the compatibility for this module to 2.7.
  9. We just found our first easteregg!Site updated from #processwire 2.7 to 3.0 via @kfinteractive, next stop: @simpholders

  10. If you want to use this module with PW3.x (and only PW3.x), please pull branch feature/devns. It needs a bit more testing before I'll release it. first backup your installation after upgrading the module, go to module settings, have a look at the settings – you may have to adapt something Whats new: messages will be saved as pages instead of repeater items you have to define a parent page, all messages created will live under this parent the page name starts with the current timestamp, you could add additional fields which should be appended field selection: you can existing fields or fill in field names, after the module are saved, for each name a field will be created manage settings like field type, required, additional error checks for each field after the module settings are saved, all existing repeater items will be converted to pages no more template creation, ProcessWire API renders the form (you can adapt the markup) you may have to translate error and success messages Have a look at the latest readme to get more information. I would love to get some feedback
  11. Replacing the php tag with the one containing the namespace isn't the solution. Modules without namespace declarations should also function in PW3.x. At the moment I'm working on a new version supporting PW3.x. I guess I'll finish that this week (the next release will provide further improvements as well).
  12. I added an option to disable multi-language fields. In field settings for Image Extra Fields there is a new checkbox "Disable multi-language fields?". Please pull branch develop to get this new feature. btw: branch develop is ProcessWire 3.x ready but it needs a bit more testing before I'll create a new release.
  13. hi, When comments are disabled and I access Blog Dashboard, I receive the following error: ProcessWire: ProcessBlog: SQLSTATE[42S02]: Base table or view not found: Table 'xxx.field_blog_comments' doesn't exist I sent a little pull request which wraps the relevant part in a condition. I know, this module isn't flagged as ProcessWire 3.x ready, but I want to tell you anyway: JqueryFancybox isn't part of the Jquery core module anymore. I added this module manually and now the dashboard works as expected. Maybe you would suggest using JqueryMagnific instead in a 3.x ready release, which still is part of the core.
  14. I sent two pull requests: TemplateEngineTwig: adds setMultiple and latest twig version using composer TemplateEngineFactory: adds setMultiple and renderChunk methods Example: How to use a chunk In template file: /site/templates/view/template.twig <?php foreach ($nav_pages as $p): ?> <?php $page->renderChunk('chunks/nav-item', array('page' => $p)); ?> <?php endforeach; ?> /site/templates/chunks/nav-item.php <?php namespace ProcessWire; $foo = 'do some logic // something with the contextual data'; $author = $this->page->createdUser; $view->setMultiple( array( 'author' => $author, 'item' => $this->page, 'foo' => $foo )); /site/templates/view/chunks/nav-item.tpl Author: <?= $author ?> <br /> <a href="<?= $item->url ?>" title="<?= $foo ?>"> <?= $item->title ?> </a>
  15. Using this solution I had to loop twice over all blog posts and this is exactly what I want to avoid. I do much more (especially markup stuff) inside the loop which I don't want to construct in php. I would love to have the possibility to load a related php file for a chunk. $chunk = $factory->load('chunks/pager'); should load /templates/chunks/pager.php where I can do some php stuff and assign variables to /templates/view/chunks/pager.tmpl. Do you see any possibility to achieve this? By the way: I added a "setMultiple" method inside your factory to be able to submit more than one property at once: // get posts $posts = $pages->find("xxx"); $view->setMultiple(array( 'posts' => $posts, 'hello' => 'world' )); // get pager $factory = $modules->get('TemplateEngineFactory'); $chunk = $factory->load('partials/pager'); if ($chunk) { $chunk->setMultiple(array( 'posts' => $posts, 'options' => $options->pager )); $view->set('pager', $chunk->render()); } If you like it I would send a pull request. But you had to add it to all of your TemplateEngines except TemplateEngineTwig. Furthermore I updated TemplateEngineTwig: I added Debug-Mode to be able to use {{ dump() }} and I updated the twig version using composer. I could also imagine to implement a little setting "choose twig version" and add the latest versions as you did without composer. If this is fine for you (please tell me which version), I would send a pull request for this, too.
  16. Hi, one little question, maybe I just missed something. Is there a way to use a chunk inside a foreach loop? I use Twig as TemplateEngine, assume the following: /templates/blog.php ... /templates/view/blog.twig ... {% for post in posts %} {% include 'partials/intro.twig' %} {% endfor %} ... Inside this partial I need some php logic which I don't want to implement using twig. I've no idea how to archive this. If I need something related outside a loop, I write the logic inside my /templates/[name].php file, if I need some code more than once, I define it in a special prependTemplateFile (at this point I would also prefer using a related php file). I know, I could use TemplateDataProvider Page::renderChunk() method which does exactly what I need, but I would prefer using a built-in way (if there is one). Using TemplateDataProvider: {% for post in posts %} {{page.renderChunk('partials/intro.twig', post)}} {% endfor %} /dataproviders/IntroChunk.php: Logic/assign variables; /partials/intro.twig markup
  17. New version 0.6.0 brings an improved new command and a brand new module:upgrade command. I've been missing this for a very long time and finally I managed to implement it. Check if module upgrades are available. $ wireshell module:upgrade --check An upgrade is available for: - FlagPages: 0.0.8 -> 0.2.3 - ImageExtra: 0.0.1 -> 0.0.3 Download and upgrade existing module. $ wireshell module:upgrade ImageExtra An upgrade for ImageExtra is available: 0.0.3 Downloading module ImageExtra... 840.40 KB/840.40 KB ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ 100% Preparing module... Module ImageExtra downloaded successfully. Module `ImageExtra` was updated successfully.
  18. I can confirm this behaviour. Noticed this some months ago and had to use $_POST for any two dimensional input.
  19. First I want to thank you for this module I missed only one little thing and therefore I sent you a pull request. I added a litte script which adds a hash to the url when clicking an item. On the other hand, if you enter such an url, the related item will be expanded and the page scrolls to this position. This way it is possible to send an url to an editor without having to say, open this link and after that click on the third headline. https://www.domain.com/processwire/setup/admin-help/#foo
  20. What's the extension of your template files? PHP as well?
  21. One more idea. Maybe it's a SSL certificate problem. Could you try to copy this cert to such a location (you need to adapt the path): /Applications/AMPPS/extra/etc/openssl/certs/cacert.pem. Then update php.ini and restart Apache: [curl] ; A default value for the CURLOPT_CAINFO option. This is required to be an ; absolute path. curl.cainfo="/Applications/AMPPS/extra/etc/openssl/certs/cacert.pem" openssl.cafile="/Applications/AMPPS/extra/etc/openssl/certs/cacert.pem" Found on stackoverflow. I extended the error message again, added curl_error() output. Could you please pull the develop branch, test again and paste the error message?
×
×
  • Create New...