Jump to content

Module: Blog


kongondo

Recommended Posts

You won't find anything specific to Blog. I suggest you search the forums at large for something like this:

'limit page editing to the user that created that page'

https://processwire.com/talk/topic/3271-can-i-limit-page-editing-to-the-user-that-created-that-page/

Read that whole thread and modify the autoload module to suit your needs. 

  • Like 1
Link to comment
Share on other sites

Regarding "Related Posts", I have been able to implement this using one line of code :-), OK, not quite but I have chosen a different route from the previously suggested code. Thanks for the inspiration and ideas though!  I will wrap this in a new renderRelatedPosts() method in MarkupBlog. In case you are wondering, the most important line of code is this:

$related = $pages->find("template=blog-post, blog_categories=$page->blog_categories, blog_tags=$page->blog_tags, id!=$page->id, limit=3, sort=-blog_date");

I'll post details later but I will make this configurable in the new method, i.e. add options to find related posts by 'tag' OR by 'category' OR 'by both tag AND category'. There will also be an option for limit as well as sort, i.e. if limiting, e.g. to 3 related posts, what's the criteria for your '3 most important related posts'? The default will be 'most commented on related posts' sort by latest posts (blog_date).

Then, similar to the 'Related Categories', 'Related Tags' and 'See also' output that you can see in the demo Blog template files running on the left hand side navigation, one will simply need to use the method renderNav() to display Related Posts as follows in the template file 'blog-post.php':

$subNav .= $blog->renderNav(__('Related Posts'), $related);

Just wanted to post these ideas before I finalise the code in case there is something I am missing? Thanks.

Edited by kongondo
  • Like 1
Link to comment
Share on other sites

Sounds good!

In my installation I deactivated comments, that's why I havn't though about the option 'most commented on related posts' (but I really like the sort option). I have not that much blog posts so I need the following combination: find related posts by 'both tag AND category', by 'category' and by 'tag' (in that order) to fill my list.

  • Like 1
Link to comment
Share on other sites

Update: Blog version 2.3.2
 
Additions
Thanks to idea by @justb3a, I have added a new method renderRelatedPosts() to MarkupBlog.  The method returns a PageArray of posts related to the post currently being viewed or the specified blog post/page. (if related posts found, otherwise returns null). It takes four arguments as follows:


renderRelatedPosts(Page $post = null, $relatedBy = null, $limit = null, $sort = null) 

1. $postThe post whose related posts will be returned. Defaults to the current page if none specified
 
2. $relatedBy: This sets the criterion for determining how other posts are related to the current post. There are 3 possible options here:
 
a. $relatedBy = 1: posts are related by both tags AND category. This means that in order to be considered as related to the specified post, the posts to be returned must have at least one tag and at least one category in common with the specified post. This is the default relation criterion.
 
b. $relatedBy = 2: posts are related by tags ONLY. Means that at least one tag has to match the specified post's tags.
 
c. $relatedBy = 3: posts are related by categories ONLY. Means that at least one category has to match the specified post's categories.
 
3. $limit: Number of related posts to retrieve. Defaults to 3 posts.
 
4. $sort: This determines the related posts to prioritise in the find. It is especially useful when you set a $limit. It defaults to sort by blog_date DESC, meaning latest posts. You can use any other valid ProcessWire sort value, e.g. sort by title, sort by 'most commented on posts' [see example below], sort by random, etc.
 
The method returns no markup and its output can be used in a variety of ways.
 
Examples

#RELATED POSTS

##1. used in conjuction with MarkupBlog's renderNav()
##similar to 'Related Categories' in the left-hand navigation in demo Blog 'blog-post.php' template file

//CALL THE MODULE - MarkupBlog
$blog = $modules->get("MarkupBlog");

//use defaults. Related posts limited to 3, related to this post by BOTH tags AND categories, ordered by blog_date DESC
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts());

//use renderNav() markup
echo $related;

//find the 'most commented on' posts related to this post by category
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts(null, $relatedBy=3, null, '-blog_comments.count'));

//find 7 posts, ordered Alphabetically by title, related to this post by tag
$related = $blog->renderNav(__('Related Posts'), $blog->renderRelatedPosts(null, $relatedBy=2, $limit=7, 'title'));

##2. used outside blog-post.php or even outside Blog pages

$post = $pages->get(2550);

//find 5 random posts related to the specified post by BOTH tags AND categories
$related = $blog->renderNav(__('Related Articles'), $blog->renderRelatedPosts($post, null, $limit=5, 'random'));

//find the 3 'least commented on' posts related to the specified post by tags
$related = $blog->renderRelatedPosts($post, $relatedBy=2, null, 'blog_comments.count');

//find 3 posts related to the specified post by tags AND categories
$related = $blog->renderRelatedPosts($post);

//use custom markup
foreach($related as $r) echo $r->title . '<br>';

Screenshot
post-894-0-13002400-1422301690_thumb.png
 
Currently in dev branch only for testing.

  • Like 2
Link to comment
Share on other sites

Here's a quick question...

I have the URL structuring set up as option 1

So blog/posts/post but would like to change to blog/post

Can I just move the posts out of the post parent page. Or would I be right in assuming it would be better to use a htaccess rewrite and rewrite blog/posts/post to blog/post ?

Thanks all

Link to comment
Share on other sites

Having a problem uninstalling. When you uninstall you have to manually delete fields etc, BUT as you have already uninstalled you cannot access blog-> cleanup.

Could you please add a link or text above uninstall to ask "Would you like to delete the fields as well?"

as I cannot now reinstall:

SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'blog-author-30' for key 'name_parent_id'

Tried manually deleting everything in the database but still get this error

Thanks

Link to comment
Share on other sites

Having a problem uninstalling. When you uninstall you have to manually delete fields etc, BUT as you have already uninstalled you cannot access blog-> cleanup.

Well this is not true...at least not if you followed the instructions to the letter  ;).

The instructions are very clear. There is no need to manually uninstall anything in Blog 2. Uninstall is a two step process

(i). Use the Cleanup first

(ii) Uninstall the module

https://github.com/kongondo/Blog#uninstall

Uninstalling Blog is a two-step process. If you are logged in as a superuser, you will see a Blog menu item called Cleanup. It will lead to a screen with info about all the Fields, Templates, Pages and Role you are about to delete. It will also list the Blog Template Files that, if you wish, you can also delete. This utility is also useful when you want to try out the different Blog styles without uninstalling the whole Blog module. It returns Blog to the state similar to when you first installed the module. Of course, in case you want to remove Blog as well, just go ahead and uninstall in the normal way but AFTER you have cleaned-up.

To remedy your situation, you need to delete the role 'blog-author'. 

Link to comment
Share on other sites

I'm fully aware its a two step process. However I forgot about the cleanup and clicked uninstall. This is about usability and this is not usable. Considering the average user is not expected to look at the uninstall page to uninstall a module with a button called uninstall on it.
 

"Uninstall this module? After uninstalling, you may remove the modules files from the server if it is not in use by any other modules.

Uninstall

This will also uninstall other modules - MarkupBlog, BlogPublishDate"

Where does it say anything about Cleanup here?

I have already deleted the role blog-author and still get the same error. I tried deleting everything manually, twice and still get this error.

I have checked every table and field I can think of and cannot find blog-author-30.
 


 

Link to comment
Share on other sites

There should be a link back to the Cleanup which is external from the 2nd step of the install process.

1. Uninstall.
2. Install.

3. See install failure due to not cleaning up.

4. Cannot reach Cleanup page as not installed. I would put the cleanup page with the install page so it can be accessed.

5. Manually delete everything, if you miss one thing, you have to start all over again.

Solution: Create a separate link to the cleanup page highlighting the SQL syntax to drop all relevant data.
 

  • Cannot install Blog fields. Some field names already in use. These are: blog_body, blog_categories, blog_comments, blog_comments_view, blog_comments_max.

  • A role called 'blog-author' already exists!

  • Due to the above errors, the install wizard did not run. Make necessary changes and try again.

  • SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'blog-author-30' for key 'name_parent_id'

    this is after manually uninstalling and deleting everything 4 times now.

    During the install it stops halfway through saying the field already exists from the >>>CURRENT<< install attempt.

    How could it? I checked the fields it references, deleted the field and ran it again. It now says a different field already exists.

Link to comment
Share on other sites

I think with all complicated systems, and this is considerably more complicated that your average little textformatter, it is always worth reading all relevant documentation before doing anything drastic.

I speak as one who has often messed up because I didn't! :)

Like all those times in front of clients I ranted and raved because yet again, the huge tape machine in our studio was not working! 

Only for the maintenance man to come all the way up to the top floor just to turn the mains switch on.

Oops.

Link to comment
Share on other sites

This is about usability , no rants and raves and it's a very simple solution.

With all complicated systems we code and focus on documentation and quirks later which stops adopt-ability. I code to make it fool-proof. It saves a lot of time in support etc later on.

Link to comment
Share on other sites

Update: Blog version 2.3.3

In addition to the very clear instructions on how to uninstall Blog (README), I have added an even clearer textual reminder/warning in Blog's module configuration screen to first run the in-built Cleanup Utility before uninstalling the module. 

post-894-0-70552800-1422577885_thumb.png

Committed to master...(including the new renderRelatedPosts()method discussed a couple of posts up.)

See next post about a utility to help when disaster strikes, aka, despite the very visible new warning text and despite the clear instructions you somehow find yourself with Blog components left in your hands having made the mistake of first uninstalling Blog and now you can't reinstall it without going through some very tedious manual cleanup....

  • Like 1
Link to comment
Share on other sites

DISCLAIMER:

The Blog Module already provides an in-built Cleanup Utility that enables you to remove all its components. As per the instructions in the module's README, which must be thoroughly read before using the module (as instructed in the first post in this thread and in various other places), in case you wish to uninstall Blog, you FIRST have to run the Cleanup Utility whilst logged in as a Supersuser. Further, as of this writing, a clear warning text is now visible right above the uninstall button in Blog's module configuration screen reminding you of this fact. Failure to follow the correct uninstall routine means that you will not be able to reinstall Blog until you (often manually) delete all the leftover components (that the Cleanup Utility would have removed for you) - a tedious, frustrating and painful exercise. 

In case, for some reason, you did not adhere to the above instructions, I am providing in the link below code to help you automatically remove any Blog leftovers in order for you to reinstall the module (if you wish, of course) or in case you just want to clean up. 

On install, Blog stores the IDs of its main pages in its configuration settings. Uninstalling Blog means those settings are lost. Hence, if using this code, the only way to find Blog pages is by their templates which in some cases, may not be very foolproof. This and others issues are documented in the utility code linked to below. 

This code is provided as is, with no obligation on my part, without any warranty, implied or otherwise. In plain English; whilst I have thoroughly tested the code, you will be using it at your own risk for which I will bear no responsibility :-).

The code should ONLY be used in case you reversed the uninstall procedure; otherwise use the normal procedure (see README) to uninstall Blog.

Link: blogCleaner

Instructions:

  1. Back up your database and template files
  2. Log in as a Supersuser
  3. Copy and paste the Cleaner code in the link above at the very top of a template file
  4. Save the template file
  5. On the frontend, visit a page that uses that template file
  6. The Cleaner's screen will be loaded
  7. Tick the checkbox to agree you 'know what you are doing, etc..'
  8. Complete the questions about the type of Blog you had before the uninstall
  9. Run the Cleaner
  10. If no errors found a success message will be displayed
  11. In your Admin, check that things went OK (and if need be  re-run the Cleaner)
  12. Restore the template file in #3 to its previous state
  13. Save the template file
  14. Reinstall Blog (optional :-))

Screens

post-894-0-32132500-1422580593_thumb.png

post-894-0-86703200-1422580594_thumb.png

------------------------

PS: I hope none of the above comes across as rude or forceful. I'll read this again in the morning just to be sure or in case someone PM's me, whichever is the sooner :-). I will then amend as appropriate.

  • Like 2
Link to comment
Share on other sites

I have a series of blog posts on my blog.php.

It's just rendering a preview image, date, title and summary.

I want to control the order of the posts but neither 

sort=-date

or

sort=sort

is working when added to my two selectors.

         <!-- CENTRE COLUMN - MAIN -->               
          <div class="small-12 medium-9 large-9 columns ">
                <!-- START Nested Column containing featureimage and post-summary -->            
                    <?php $blogposts = $pages->find("template=blog-post"); foreach ($pages->find("template=blog-post,") as $b) {
                    echo "
					   <div class='row row-spacer'>
					     <div class='small-12 large-6 columns'><img src={$b->blog_images->first()->url} /></div>
					     <div class='small-12 large-6 columns'>
						 <div class='posts-date'>{$b->blog_date}</div>
						 <h3><a href='$b->url'>{$b->title}</a></h3>
						 {$b->blog_summary}</div>
					   </div>
					";
					} ?>
                <!-- END Nested Column containing featureimage and post-summary -->    
          </div>
Link to comment
Share on other sites

You can only sort by fields that exist in that template or internal properties (e.g., sort). There is no field called 'date' in the template 'blog-post'...unless you added it yourself? Otherwise, the following should work.

I don't know why you had two $pages->find()? Did you also add the field 'blog_summary'?

<!-- CENTRE COLUMN - MAIN -->               
<div class="small-12 medium-9 large-9 columns ">
    <!-- START Nested Column containing featureimage and post-summary -->            
        <?php $blogposts = $pages->find("template=blog-post, sort=-blog_date, sort=sort");

        foreach ($blogposts as $b) {
	        echo "
			   <div class='row row-spacer'>
			     <div class='small-12 large-6 columns'><img src={$b->blog_images->first()->url} /></div>
			     <div class='small-12 large-6 columns'>
				 <div class='posts-date'>{$b->blog_date}</div>
				 <h3><a href='$b->url'>{$b->title}</a></h3>
				 {$b->blog_summary}</div>
			   </div>
			";
		}
		?>
    <!-- END Nested Column containing featureimage and post-summary -->    
</div>
Link to comment
Share on other sites

@Kongondo

Thanks for the quick reply. I assumed the Date field was called date. As you point out, it's actually "blog_date". 

I've installed Somas Helper Field Links and this has made the field names more obvious.

I don't know why you had two $pages->find()

I'm not sure either. I don't do this in my current projects and I wondered if it was a legacy piece of code. Clearly just an error though.

Did you also add the field 'blog_summary'?

Yes, we use it for a tiny summary on the blog overview page. You probably have something like this native now but this is an older version of Blog Module I've yet to update.

Also, wanted to apologise for the abrupt request for help in the original post. My client is presenting this at 10AM this morning and informed me 30 mins prior to the meeting that they needed the posts in a particular order. The order had been fine for the past few days. Anyway, thanks again.  ^-^

Link to comment
Share on other sites

Hi Kongondo. I attempted to comment on a blog post and was redirected to [root]/#CommentForm which just booted me back to the home page.

My blog-post.php template file contains only the following code regarding blog comments:

$blogOut = $modules->get("MarkupBlog");

and

echo $page->blog_comments->render();

echo $page->blog_comments->renderForm(); 

$numComments = $page->blog_comments->count();

Here's the markup that the site outputs for the form.

<div id='CommentForm' class='CommentForm_new'>
<h3>Post Comment</h3>
<form id='CommentForm_form' action='./#CommentForm' method='post'>
	<p class='CommentForm_cite'>
		<label for='CommentForm_cite'>Your Name</label>
		<input type='text' name='cite' class='required' required='required' id='CommentForm_cite' value='' maxlength='128' />
	</p>
	<p class='CommentForm_email'>
		<label for='CommentForm_email'>Your E-Mail</label>
		<input type='text' name='email' class='required email' required='required' id='CommentForm_email' value='' maxlength='255' />
	</p>
	<p class='CommentForm_text'>
		<label for='CommentForm_text'>Comments</label>
		<textarea name='text' class='required' required='required' id='CommentForm_text' rows='5' cols='50'></textarea>
	</p>
	<p class='CommentForm_submit'>
		<button type='submit' name='CommentForm_submit' id='CommentForm_submit' value='1'>Submit</button>
		<input type='hidden' name='page_id' value='1449' />
	</p>
</form>
</div><!--/CommentForm-->

Without changing the module I'm not sure how to fix this. I checked the Settings in Blog Admin but nothing seems to control the form directly.

Link to comment
Share on other sites

Not sure what funkiness is going on there. Have a look at the demo blog-post.php. All you need to render both comments and the form is MarkupBlog's method renderComments() (form will only be displayed if the page uses the template blog-post).

$blog = $modules->get("MarkupBlog");
echo $blog->renderComments($page->blog_comments);
Edited by kongondo
Link to comment
Share on other sites

Aah, I think I know what is happening....It is not directly related to Blog but the settings of your comments field. Edit the field blog_comments. Go to..

Admin > Setup > Fields > Edit Field: blog_comments. Go to the Details tab. In the second row on that settings page, under Redirect after comment post?, I think you have that checkbox checked. Read the info there and decide whether you want to have it redirect or not. 

Link to comment
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...