Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by tcnet

  1. I updated the module to 1.0.4 and added an option to specify the Return-Path in the email header. This option is blank by default.
  2. Thanks for this info. But I by my self encountered the opposite on some systems. Not adding this line won't send the email.
  3. That error message means that WireMail can not send the email. Maybe your mailer implementation doesn't work.
  4. I made changes in the upgrade function. Please upgrade to version 1.1.7.
  5. Please give me 24 hours. I have another work too.
  6. Can you check which mySQL version?
  7. Ok. I don't know what you doing. The upgrade shold work. I guess you changed the database manually.
  8. I made a change in line 389. It seems that getenv('REMOTE_ADDR') doesn't work with local IP addresses. Please upgrade to version 1.1.6.
  9. Why "no ip address"? Where you know this?
  10. There are not a single ERROR MESSAGE in your post! These are Warnings and Notices which you get when you run ProcessWire in debug mode. And why they not appear? Because your ProcessWire DON'T run in debug mode.
  11. You will see "PHP notices" if you run your ProcessWire in debug mode. Please read the description for the debug mode. The debug mode is not intended for productive usage. Please turn off debug mode and you will see that everything works fine.
  12. Yes, the Debug Mode Tools-Panel is available. Please see the 3rd arrow in the last screenshot. But not all debug information seems to be available. I cannot see any PDO-Query or AutoLoad. Sorry.
  13. What's new in ProcessWire 3.0.163? See: https://weekly.pw/issue/324/ I created this module before ProcessWire 3.0.163. I thought it's time to publish it. If it is not desirable, I remove it again. Just tell me.
  14. This module for ProcessWire enables the debug mode to bypass the restriction to install modules. This is useful if you are tired to manually set the debug mode in the configuration. Note Please note that this module doesn't replace the real debug mode in the configuration file /site/config.php. With this module you will not receive any errors/notices/warnings like in the real debug mode. It serves only to bypass the restriction to install modules. Installation To install this module you have to enable the real debug mode. After installation you should deactivate debug mode again. To enable the real debug mode, download /site/config.php via FTP and open it in a text editor. Look for a line where you can find $config->debug = false; change it to $config->debug = true; save the file and upload it again. After module installation change it back to $config->debug = false;. For all future module installations, you just have to enable the debug mode in the module settings like described below. After module installation, you should deactivate it in the same way. Settings The settings for this module are located in the menu Modules=>Configure=>DebugModeSwitch. Enable or deactivate debug mode Set the checkmark (1) and click the submit button (2) will enable the debug mode (3). The debug mode can be also restricted for superusers only (4). Links ProcessWire module directory: https://processwire.com/modules/debug-mode-switch/ Github: https://github.com/techcnet/DebugModeSwitch
  15. The link doesn't work because the site-profile is still waiting for approval. Please note that a thread in this forum here is required to submit a new module or site-profile. Please be patient a few days. Thank you!
  16. This site profile for ProcessWire offers a simple, multilingual and responsive blog which doesn't require any module. It works exclusively with some template files. See: https://processwire.com/modules/site-simple-blog-multilanguage/ Installation This site profile is intended for use with a new installation of ProcessWire. Download ProcessWire, extract all files and folders and upload it into your web server folder. Download the site profile, extract the simple-blog-multilanguage folder and upload it into the same folder. Start the installation. When prompted for Site Installation Profile select Simple and Multilingual Blog Profile for ProcessWire 3x and continue with installation.
  17. Please show me an example where your dump() function returns the output. I got it only to work with echoing the output which is not what I want.
  18. Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu. The following conditions must be met for the module to work properly: Session files Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions. Serialize handler In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer. Session data The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer. Links ProcessWire module directory github.com
  19. If you exchanged the module file then the exception will occurring in a different line ynd you will not get the same error message. If you deleted table process_pageviewstat_main and installed version 1.1.1 then process_pageviewstat_main will recreated with column usr. But in this case you will not get the same error message. I guess you loading your pages from the browser cache.
  20. Did you replaced the file or not? What's the error message after you replaced the file? How you cleaned the database? Did you deleted the table process_pageviewstat_main in the database or not? Did you followed my instruction: Please delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat. Then execute the upgrade again. If you get the error again then delete ProcessPageViewStat and rename .ProcessPageViewStat to ProcessPageViewStat and uninstall the module from then module page and install it again.
  21. Did solved the problem? You can also replace the module file in the attachment of this message. It encloses the database execution in line 376 with a try-catch. So you are able to click the refresh button without error message. The refresh button should call the upgrade funtion or something is wrong in your PW. ProcessPageViewStat.module
  22. Or you have to add a new int column to process_pageviewstat_main named usr. This is what the upgrade function does.
  • Create New...