Jump to content

Recommended Posts

I haven't had a chance to play with this yet, but I know it will be used on an upcoming site - just wanted to say how great it looks and most importantly how impressive the documentation looks to be - love the use of Github wiki!

  • Like 1

Share this post


Link to post
Share on other sites

You were probably going to have countless issues if you'd played with it before yesterday as I didn't test across multiple PHP/MySQL versions. (I'm lazy like that.)

But all seems to be good now - lemme know if you bump into any issues.

Was going to host the docs myself... but the tools are there, so use them - hehe!

:)

Share this post


Link to post
Share on other sites

The mapping collection API has been modified:

  1. Method has changed from addCollection() to collection() due to:
  2. the fact that it now picks up if a collection already exists so that it can add data to it.

Docs updated.

(Thanks Dave.)

Share this post


Link to post
Share on other sites

Update: No, something's gone wrong there. Don't update just yet.

Fixed.

Edited by Mike Anthony

Share this post


Link to post
Share on other sites

Just fixed up a little issue regarding the first TIMESTAMP column being auto-updated.

Basically swapped the created_at and updated_at columns around, and removed the updated_at = CURRENT_TIMESTAMP bit from the SQL template used for updating mapping collections.

I could have just defaulted to NULL for both of these timestamps, but I think this is better. Who cares about column order, anyway?

Share this post


Link to post
Share on other sites

Okay, so after all those fixes, my testing seems to show that everything is stable. Everyone agree? I'd like to set this to stable in GH and in the directory.

  • Like 1

Share this post


Link to post
Share on other sites

I will probably be able to test it on the weekend throughly, but so far it looks stable and works like a charm.

  • Like 1

Share this post


Link to post
Share on other sites

Are we ready to go ahead and make this stable? I haven't encountered any further issues...

Hell yeah. I didn't encounter any further problems, but I haven't done the big test yet. 

  • Like 1

Share this post


Link to post
Share on other sites

I've just installed the module, but it seems the redirect is to late and I get a "Cannot modify header information - headers already sent by" error.

Edit:

Changing the hook from addHook() to addHookBefore() solved the issue.

Share this post


Link to post
Share on other sites

I've just installed the module, but it seems the redirect is to late and I get a "Cannot modify header information - headers already sent by" error.

Edit:

Changing the hook from addHook() to addHookBefore() solved the issue.

What sent headers first?

Share this post


Link to post
Share on other sites

My templates _init.php, but even as I removed that part the rendering of mustache in a appended TemplateFile was earlier than Jumplinks.

Share this post


Link to post
Share on other sites

I see. So there could be a lot of scenarios involved. Think it would be worth it to change the hook to something way early, and then check to see if a page representing the request exists? We could also add a configuration option that defaults the hook to pageNotFound, but allows you to specify if something is rendering output before the 404. Would be a simple checkbox that says, "Check Jumplinks in an early event - this prevents interruptions from other hooks/templates/etc."

What do you think?

Side note: my Redirects module for Bolt ties into a very early app event. Sure, the caveat is that pages that exist with the request uri are ignored, but we could add a simple check. Perhaps it would also perform redirects faster, as less things boot up?

Share this post


Link to post
Share on other sites

I think the hook is the right one, just addHookBefore does force template rendering to wait for your hooked function to finish, while addHook doesn't seem to do this.

Share this post


Link to post
Share on other sites

I think we're ready for stable. I'm first going to switch over to prepared statements - silly me for not doing this first. Once done, I'll switch over to stable.

Share this post


Link to post
Share on other sites

Version Bump to 1.1.0

Module is now stable (it looks to be, at least).

  1. Now using PDO Prepared Statements
  2. Tables honour responsiveness now - there was an issue with tfoot, so I just hid it from mobile...
  3. Various bug fixes
  4. No schema changes

Let me know if you bump into anything weird.  ;)

Oh, and there's this issue - anyone have any input on that? (Personally, I prefer to have full control... Don't really like modules making decisions for me.)

  • Like 3

Share this post


Link to post
Share on other sites

Version Bump to 1.1.1

  1. Using minified JS (manual call)
  2. Refactor SQL object
  3. Various other changes/fixes
  4. No schema changes

(And GitHub is under attack - boy, how I battled to commit the changes... Finally slipped through after about 20 minutes of trying.)

  • Like 2

Share this post


Link to post
Share on other sites

Version Bump to 1.1.2

  1. Correct page-check behaviour (was using name, now using URI)
  2. Use commitJumplink in CSV importer
  3. No schema changes
  • Like 2

Share this post


Link to post
Share on other sites

Version Bump to 1.1.3

  1. Error-control for REQUEST_URI (previously threw an exception regarding it being undefined when using wireshell)
  2. No schema changes
  • Like 1

Share this post


Link to post
Share on other sites

I actually had to uninstall the module - it was causing excessive mysql database connections (not usage) and my webserver nearly stalled.

Maybe I run into a loop or something?

I was redirecting from an old Drupal website to PW and used about 70 simple type redirects, such as sources  /drupal/page1/   

Got this (on the latest PW dev)

Error:

Exception: SQLSTATE[HY000]: General error: 1116 Too many tables; MySQL can only use 61 tables in a join (in /wire/core/PageFinder.php line 300)

Error:

Exception: DB connect error 1203 - User already has more than 'max_user_connections' active connections (in /wire/core/Database.php line 68)

I cannot say 100% that this was Jumplinks. I just noted that the performance was back to normal after I uninstalled the module.

So this is just for information in case anyone else can confirm this.

Share this post


Link to post
Share on other sites

Thanks for your post. :-)

Looks like another module is doing that. Jumplinks only creates two tables (one for jumplinks, and another for mapping collections).

In terms of performance, I'm unable to test that sort of thing. Are you saying that those errors go away when you uninstall Jumplinks? Do you have the same issue if you use ProcessRedirects?

If you (or anyone else) could provide me with more information, that would be great. Otherwise, I can't determine what's going on.

Share this post


Link to post
Share on other sites

On the topic of performance, I'm now wondering if I should set up a cache system for Jumplinks. It was mentioned by Antti a while back that Jumplinks is already feature-rich, but I think that caching redirects will actually be a life-saver for some users with large sites. At the end of the day, running the regex engine for every incoming request is sure to be a big performance hit on any server (the way I see it).

I'm sure everyone agrees this should be added?

There are also a few other fixes and enhancements in the pipeline, the most important one involves optional query-strings (much like the QSA flag for mod_rewrite). At the moment, if you want to match something.php and something.php?foo is requested, the redirect will not occur. In order to get it to work, you'd need to add {all} on the end of the source URI, which is, quite frankly, not the best way of doing it.

  • Like 3

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...