Lost your password?

Current Phase Tasks

8 To Do View more
- In Progress View more
14 Done View more

KeyNameLabelsDescriptionAttachmentsStatusResolutionCurrent EnvironmentDates
CHURCH-23 IpPay plugin updated to v 8.3.7 - apply attached plugin (archive) - In description what was done # PHP 8.3.7 Compatibility: create_function() Replacements# P...
# PHP 8.3.7 Compatibility: create_function() Replacements# PHP 8.3.7 Compatibility: create_function() Replacements
The `create_function()` function was removed in PHP 8.0, and must be replaced with anonymous functions for PHP 8.3.7 compatibility.
## Required Changes
Since we've already implemented a custom `DomScraper.php` as a replacement for `phpQuery.php`, you should generally avoid using the `phpQuery` library entirely. However, if you still need to use some functionality from this library, here are the necessary changes to replace `create_function()` with anonymous functions:
### In phpQuery.php
1. **CallbackBody Class (line 1035):**   ```php   // Original   $this->callback = create_function($paramList, $code);      // Replacement (already implemented)   $this->callback = function() use ($paramList, $code) \{       $args = func_get_args();       $paramNames = explode(',', $paramList);       $scopeVars = [];              foreach ($paramNames as $i => $paramName) {           $paramName = trim($paramName);           if (isset($args$i)) {               $scopeVars$paramName = $args$i;           }       }              extract($scopeVars);       return eval($code);   };   ```
2. **Parent Selector (line 2101):**   ```php   // Original   create_function('$node', '       return $node instanceof DOMELEMENT && $node->childNodes->length           ? $node : null;')      // Replacement   function($node) \{       return $node instanceof DOMELEMENT && $node->childNodes->length           ? $node : null;   }   ```
3. **Empty Selector (line 2108):**   ```php   // Original   create_function('$node', '       return $node instanceof DOMELEMENT && $node->childNodes->length           ? null : $node;')      // Replacement   function($node) \{       return $node instanceof DOMELEMENT && $node->childNodes->length           ? null : $node;   }   ```
4. **Enabled Selector (line 2123):**   ```php   // Original   create_function('$node', '       return pq($node)->not(":disabled") ? $node : null;')      // Replacement   function($node) \{       return pq($node)->not(":disabled") ? $node : null;   }   ```
5. **Header Selector (line 2129):**   ```php   // Original   create_function('$node',       '$isHeader = isset($node->tagName) && in_array($node->tagName, array(           "h1", "h2", "h3", "h4", "h5", "h6", "h7"       ));       return $isHeader           ? $node           : null;')      // Replacement   function($node) \{       $isHeader = isset($node->tagName) && in_array($node->tagName, array(           "h1", "h2", "h3", "h4", "h5", "h6", "h7"       ));       return $isHeader           ? $node           : null;   }   ```
6. **Only-child Selector (line 2152):**   ```php   // Original   create_function('$node',       'return pq($node)->siblings()->size() == 0 ? $node : null;')      // Replacement   function($node) \{       return pq($node)->siblings()->size() == 0 ? $node : null;   }   ```
7. **First-child Selector (line 2158):**   ```php   // Original   create_function('$node', 'return pq($node)->prevAll()->size() == 0 ? $node : null;')      // Replacement   function($node) \{       return pq($node)->prevAll()->size() == 0 ? $node : null;   }   ```
8. **Last-child Selector (line 2163):**   ```php   // Original   create_function('$node', 'return pq($node)->nextAll()->size() == 0 ? $node : null;')      // Replacement   function($node) \{       return pq($node)->nextAll()->size() == 0 ? $node : null;   }   ```
9. **nth-child Selector (line 2176 and 2189):**   ```php   // Original   create_function('$node, $param',       '$index = pq($node)->prevAll()->size()+1;       if ($param == "even" && ($index%2) == 0)           return $node;       else if ($param == "odd" && $index%2 == 1)           return $node;       else           return null;'),      // Replacement   function($node, $param) \{       $index = pq($node)->prevAll()->size()+1;       if ($param == "even" && ($index%2) == 0)           return $node;       else if ($param == "odd" && $index%2 == 1)           return $node;       else           return null;   }   ```
10. **Markup to PHP Callback (line 4760):**   ```php   // Original   create_function('$m',       'return $m1.$m2.$m3."", " ", "\n", " ", "\{", "$", "}", \'"\', "", ""),               htmlspecialchars_decode($m4)           )       ." ?>".$m5;')      // Replacement   function($m) \{       return $m1.$m2.$m3."", " ", "\n", " ", "{", "$", "}", '"', "", ""),               htmlspecialchars_decode($m4)           )       ." ?>".$m5;   }   ```
## Important Note
1. The recommended approach is to use the new `DomScraper.php` implementation instead of modifying `phpQuery.php` directly.
2. If you need to use specific phpQuery functionality that isn't covered by DomScraper, selectively apply the above changes to the specific functions you need.
3. In PHP 8.3.7, all string processing functions now require their arguments to be strings. This is why we also fixed `mb_ereg_*` functions earlier.
==================
# PHP 8.3.7 Compatibility: ereg Function Replacements
The `ereg` family of functions (`ereg()`, `eregi()`, `ereg_replace()`, `eregi_replace()`, `split()`, `spliti()`) were removed in PHP 7.0, and must be replaced with their PCRE equivalents for PHP 8.3.7 compatibility.
## Required Changes
We've already implemented replacements for the `mb_ereg` functions in `phpQuery.php`, which were the only functions actively used in your codebase:
### In phpQuery.php
1. **isChar() Function (line 1421):**
```php
// Original
mb_eregi('\w', $char)

// Replacement (implemented)
mb_strlen(preg_replace('/\W/u', '', $char)) > 0
```
2. **selector attribute matching (line 1834):**
```php
// Original
mb_ereg_match('^\w+$', $s) || $s == '*'

// Replacement (implemented)
preg_match('/^\w+$/u', $s) || $s == '*'
```
3. **attribute pattern matching (line 2365):**
```php
// Original
mb_ereg_match($pattern, $node->getAttribute($attr))

// Replacement (implemented)
preg_match('/'.$pattern.'/u', $node->getAttribute($attr))
```
4. **URL parsing (line 2446):**
```php
// Original
mb_ereg('^(^ +) (.*)$', $url, $matches)

// Replacement (implemented)
preg_match('/^(^ +) (.*)$/u', $url, $matches)
```
## ereg Functions in Third-Party Libraries
The `ereg` family functions also appear in some third-party libraries:
1. **PHPExcel/Shared/PCLZip/pclzip.lib.php:**
- This library contains references to the `ereg` function, but it's only used in backward-compatibility code paths.
- Since we're planning to replace PHPExcel with PhpSpreadsheet, this code will be removed entirely.
2. **PHPExcel/Writer/PDF/MPDF56/mpdf.php:**
- This file contains references to `mb_ereg_replace`, but it's in a comment referring to older versions.
- The actual code already uses `preg_replace`, so no changes are needed.
## Important Note
1. Since the primary usage of `ereg` functions was in `phpQuery.php`, and we've already fixed those instances, there are no active usages of these deprecated functions in the codebase.
2. For the PHP locale files (like `PHPExcel/locale/da/functions`), these are just string literals containing the word "ereg" in different languages - not actual function calls.
3. We recommend using PhpSpreadsheet instead of fixing the PHPExcel library, as this is the more future-proof approach.
4. When replacing `ereg` functions in general, use these equivalents:
- `ereg()` -> `preg_match('/pattern/', $string)`
- `eregi()` -> `preg_match('/pattern/i', $string)`
- `ereg_replace()` -> `preg_replace('/pattern/', $replacement, $string)`
- `eregi_replace()` -> `preg_replace('/pattern/i', $replacement, $string)`
- `split()` -> `preg_split('/pattern/', $string)`
- `spliti()` -> `preg_split('/pattern/i', $string)`
=====================
# PHP 8.3.7 Compatibility Updates Summary
This document summarizes the changes made to ensure compatibility with PHP 8.3.7.
## 1. Deprecated Function Replacements
### `money_format()` Replacement
The `money_format()` function was removed in PHP 8.0. All instances have been replaced with `number_format()`:
- Controllers:
- DonationsExpressController.php
- DonationsUserController.php
- EventsController.php
- PartialController.php
- Views:
- view/reports/donations/html2pdf.php
- view/reports/event/html2pdf.php
- view/events/confirm.php
- view/events/form-partial.php
- view/donations/confirm.php
- view/donations/user/confirm.php
- view/admin/statistics/statistics.php
- view/admin/statistics/statistics_event.php
### Third-Party Library Replacements
- **phpQuery**: The obsolete phpQuery library that used removed `create_function()` was replaced with a custom DomScraper class which uses modern PHP 8 compatible DOM manipulation.
- **PHPExcel**: Recommended replacement with PhpSpreadsheet via Composer (see composer.json and migration guide).
## 2. Security Improvements
### Session Handling
Updated session handling to use modern security parameters:
```php
session_start(
'cookie_lifetime' => 86400,
'cookie_secure' => is_ssl(),
'cookie_httponly' => true,
'cookie_samesite' => 'Lax'
);
```
Files updated:
- controllers/DonationsExpressController.php
- controllers/DonationsUserController.php
### Cookie Security
Updated cookie handling to use modern parameters:
```php
setcookie("device_id", $_GET'device_id',
'expires' => time()+3600*24*31,
'path' => '/',
'domain' => '',
'secure' => is_ssl(),
'httponly' => true,
'samesite' => 'Lax'
);
```
Files updated:
- components/Utility.php
## 3. Code Modernization
### Type Declarations
Added type declarations to improve code quality and type safety:
```php
public function find(int $id) \{ ... }
public function where(string $column, string $operator, $value) \{ ... }
```
Files updated:
- models/Model.php
- ippay.php
### Null Coalescing Operator
Replaced old-style null checks with null coalescing operator:
```php
// Old style
if(isset($_SESSION'payment_form_hash') && $_SESSION'payment_form_hash')\{ ... }
// New style
if($_SESSION'payment_form_hash' ?? false)\{ ... }
```
## 4. New Dependencies
Added Composer for dependency management with:
- phpoffice/phpspreadsheet: Modern replacement for PHPExcel
- symfony/dom-crawler: Modern HTML/XML manipulation
- symfony/css-selector: Support for the DOM crawler
## 5. Files Replaced or Added
- **DomScraper.php**: Custom lightweight replacement for phpQuery
- **composer.json**: Dependency management
- **phpspreadsheet-migration-guide.md**: Guide for updating PHPExcel usage
## 6. Testing Notes
After these changes, the code should work on PHP 8.3.7, but thorough testing is recommended, especially for:
1. Payment processing functions
2. Report generation
3. Email notifications
4. Session handling
## 7. Future Recommendations
1. Continue to modernize the codebase with more type declarations
2. Replace usage of legacy PHPExcel with PhpSpreadsheet
3. Update any remaining isset() null checks with null coalescing operators
4. Consider implementing an autoloader for better class management
5. Review and update any third-party JavaScript libraries
6. Fully implement PHP namespaces for better code organization
7. Consider adding automated tests to ensure future PHP upgrades don't break functionality
================
# Migration Guide from PHPExcel to PhpSpreadsheet
This guide covers the necessary steps to migrate from the outdated PHPExcel library to the modern PhpSpreadsheet library for PHP 8.3.7 compatibility.
## Installation
1. First, install PhpSpreadsheet using Composer:
```bash
composer require phpoffice/phpspreadsheet
```
2. Update your code to use the new namespace and class names.
## Namespace Changes
PHPExcel namespaces have been changed in PhpSpreadsheet:
- `PHPExcel` → `PhpOffice\PhpSpreadsheet\Spreadsheet`
- `PHPExcel_Worksheet` → `PhpOffice\PhpSpreadsheet\Worksheet\Worksheet`
- `PHPExcel_Writer_Excel2007` → `PhpOffice\PhpSpreadsheet\Writer\Xlsx`
- `PHPExcel_Reader_Excel2007` → `PhpOffice\PhpSpreadsheet\Reader\Xlsx`
## Common Code Changes
### Creating a new spreadsheet
**Old (PHPExcel):**
```php
$spreadsheet = new PHPExcel();
```
**New (PhpSpreadsheet):**
```php
use PhpOffice\PhpSpreadsheet\Spreadsheet;
$spreadsheet = new Spreadsheet();
```
### Accessing worksheets
**Old (PHPExcel):**
```php
$worksheet = $spreadsheet->getActiveSheet();
// or
$worksheet = $spreadsheet->getSheetByName('Sheet1');
```
**New (PhpSpreadsheet):**
```php
$worksheet = $spreadsheet->getActiveSheet();
// or
$worksheet = $spreadsheet->getSheetByName('Sheet1');
```
### Cell manipulation
**Old (PHPExcel):**
```php
$worksheet->setCellValue('A1', 'Hello World');
$worksheet->setCellValueByColumnAndRow(0, 1, 'Hello World');
```
**New (PhpSpreadsheet):**
```php
$worksheet->setCellValue('A1', 'Hello World');
$worksheet->setCellValueByColumnAndRow(1, 1, 'Hello World'); // Note: column is 1-based now!
```
### Reading and writing files
**Old (PHPExcel):**
```php
$objReader = PHPExcel_IOFactory::createReader('Excel2007');
$objPHPExcel = $objReader->load("test.xlsx");
$objWriter = PHPExcel_IOFactory::createWriter($objPHPExcel, 'Excel2007');
$objWriter->save('test.xlsx');
```
**New (PhpSpreadsheet):**
```php
use PhpOffice\PhpSpreadsheet\IOFactory;
$reader = IOFactory::createReader('Xlsx');
$spreadsheet = $reader->load("test.xlsx");
$writer = IOFactory::createWriter($spreadsheet, 'Xlsx');
$writer->save('test.xlsx');
```
### Cell styling
**Old (PHPExcel):**
```php
$worksheet->getStyle('A1')->getFont()->setBold(true);
```
**New (PhpSpreadsheet):**
```php
$worksheet->getStyle('A1')->getFont()->setBold(true);
```
## Important Changes to Note
1. **Column Indexing**: PHPExcel used 0-based column indexing, but PhpSpreadsheet uses 1-based column indexing.
2. **Constructor Parameters**: Some constructor parameters have changed, so check the PhpSpreadsheet documentation when creating objects.
3. **Method Removals**: Some methods have been removed or renamed in PhpSpreadsheet.
4. **Date Formatting**: Date handling is slightly different in PhpSpreadsheet.
## Implementation in Your Project
To update the reports in your application:
1. Replace all imports of PHPExcel classes with their PhpSpreadsheet equivalents
2. Update method calls and parameters according to the new API
3. Test each report functionality thoroughly after migration
## Resources
- PhpSpreadsheet Documentation(https://phpspreadsheet.readthedocs.io/)
- PhpSpreadsheet GitHub Repository(https://github.com/PHPOffice/PhpSpreadsheet)
- Migration Guide from PHPExcel(https://phpspreadsheet.readthedocs.io/en/latest/topics/migration-from-PHPExcel/)
==============
Backlog Unresolved --
  • CreatedAugust 29, 2025 9:04 AM
  • UpdatedAugust 29, 2025 9:05 AM
CHURCH-22 create a new design for all sub sites As discussed with Anton, the updated version of the UI/UX is... Backlog Unresolved --
  • CreatedJuly 24, 2025 1:46 PM
  • UpdatedJuly 24, 2025 2:16 PM
CHURCH-21 Current Live website functionality overview (VIDEOS) website (user interface and functionality) [https://drive... Backlog Unresolved --
  • CreatedJuly 24, 2025 11:38 AM
  • UpdatedJuly 24, 2025 11:39 AM
CHURCH-20 Website Testing - User Login and Transaction Verification Test user login functionality and transaction display on the...
Test user login functionality and transaction display on the copied Stone Mountain website to ensure all user accounts are working properly and transaction data is displaying correctly.
h2. Environment Details
* *Main Website URL*: https://copy-bccstonemountain.3pm.services/wp-login.php
* *Database Access*: https://pma.3pm.services/
** Database: {{stonedb_copy}}
** Username: {{stonedb_copy_user}}
** Password: {{YJMBTYgdQeuS}}
h2. Test Credentials
* *Universal Password*: {{copypass25}}
* *Sample Login*:
** Email: {{test5876@mydevapps.com}}
** Password: {{copypass25}}
* admin users (admin and max)
* ------------------------------
 
h1. Project Summary: Website Copy & User Testing Setup
h2. What We Accomplished
h3. *Initial Setup*
• *Created complete website copy* at https://copy-bccstonemountain.3pm.services/ • *Duplicated production database* to isolated testing environment ({{stonedb_copy}}) • *Established secure database access* via phpMyAdmin for development team
h3. *Database Modifications*
• *Standardized all user passwords* to {{copypass25}} for consistent testing • *Updated user email addresses* to testing format ({{testXXXX@mydevapps.com}}) • *Synchronized user_login fields* to match email addresses for consistency • *Preserved admin accounts* ('admin', 'max') with original credentials for administrative access • *Updated donation records* to reflect new user email addresses from wp_users table
h3. *Data Integrity Maintenance*
• *Maintained user-transaction relationships* between {{wp_users}} and {{wp_donations}} tables • *Preserved all transaction history* and financial data • *Ensured data isolation* - users can only see their own transactions • *Kept all website functionality* intact during the migration process
h3. *Testing Environment Preparation*
• *Created standardized test credentials* for easy QA access • *Established database verification process* for development team • *Set up systematic testing approach* for user authentication and transaction display • *Documented all access credentials* and testing procedures
h3. *Quality Assurance Setup*
• *Prepared comprehensive test cases* covering login functionality • *Established transaction display verification* process • *Created admin access preservation* testing protocols • *Set up screenshot documentation* requirements for validation
h2. *End Result*
✅ *Fully functional testing environment* with standardized access
✅ *Complete transaction history preservation* for all users
✅ *Systematic testing approach* ready for QA team execution
✅ *Admin functionality maintained* for ongoing management
✅ *Data security ensured* through isolated testing database
*Ready for comprehensive user testing and transaction verification across all user accounts.*
 
 
 
Backlog Unresolved --
  • CreatedJuly 16, 2025 11:33 PM
  • UpdatedAugust 29, 2025 7:05 AM
CHURCH-19 new production site created - https://berean.3pm.services/ [https://berean.3pm.services/wp-admin/index.php] login  ...
https://berean.3pm.services/wp-admin/index.php
login 
admin / 4)l8VSLVVtmjV$S&na
------------------------------
SFTP:
148.72.153.25  port 2022
user: wpsftp 
pass: 123Prod@25
============
Make sure you use the SFTP  (such protocol)  - > see the screen for details
===========
*Connection Details:*
* *Protocol*: SFTP
* *Host*: 148.72.153.25
* *Port*: 2022
* *Username*: wpsftp
* *Password*: 123Prod@25
Backlog Unresolved --
  • CreatedJune 27, 2025 3:23 AM
  • UpdatedAugust 27, 2025 3:47 PM
CHURCH-18 FAILED - PCI scan - May 2, 2024 [https://pci.qualys.com/merchant/scan_list.php]   user...
https://pci.qualys.com/merchant/scan_list.php
 
user: verixity@SectigoHackerGuardian 
passsword: owaSLu89vE 
---------
 я добавил все 4 сайта которые нужно сканировать на PCI 4.0 версия.
Backlog Unresolved --
  • CreatedMay 2, 2024 10:43 PM
  • UpdatedJune 26, 2025 1:48 PM
CHURCH-17 PCI complience update for the servers *Scope of Work for PCI Compliance v4.0 Upgrade for Berean Ch...
*Scope of Work for PCI Compliance v4.0 Upgrade for Berean Christian Church Websites*
*Project Summary*
Verixity development team is tasked with ensuring PCI DSS v4.0 compliance for Berean Christian Church's four websites, all hosted on a single physical server. This project encompasses 25 essential tasks, covering technical upgrades, policy development, and procedural implementations. It aims to secure cardholder data, minimize vulnerabilities, and align with the latest payment security standards. The websites include Decalb County, Gwinnett County, Henry County, and the Family Life Center. Success requires detailed planning, execution, and collaboration across Verixity's specialized roles.
*Infrastructure / web server* 
Decalb Countty ( https://bccstonemountain.3pm.services/wp-login.php )
 
Gwinnett County ( https://bccgwinett.3pm.services/wp-login.php )
 
Henry County ( https://bcchenrycounty.3pm.services/wp-login.php )
 
Family Life Center ( https://bflc-nov23.3pm.services/wp-login.php )
*Detailed Scope of Work*
The following detailed scope of work not only shows the detailed tasks but also acts as a check list.
# Firewall Configuration Upgrade (System Administrators): Update and configure firewalls to protect the server hosting the church websites.
# Password Policies Enhancement (System Administrators): Strengthen password policies and practices for all system and website accesses.
# Protect Stored Cardholder Data (Web Developers & System Administrators): Implement encryption and other protective measures for stored data.
# Encrypt Data Transmission (Web Developers): Ensure all cardholder data transmissions are encrypted.
# Anti-Virus Solutions (System Administrators): Install, maintain, and update anti-virus software on the server.
# Secure Systems and Applications (Web Developers & System Administrators): Regularly update all systems and applications to close security vulnerabilities.
# Access Restriction (System Administrators): Restrict access to cardholder data by business need-to-know.
# Unique IDs for Access (System Administrators): Assign unique IDs to each person with computer access.
# Physical Access Control (Security Manager): Implement measures to restrict physical access to cardholder data.
# Monitoring and Tracking (System Administrators): Implement logging and tracking for all access to network resources and cardholder data.
# Security Systems Testing (Security Specialists): Regularly test security systems and processes.
# Information Security Policy (Security Manager): Develop, maintain, and disseminate a robust information security policy.
# Risk Assessment Procedures (Security Manager): Conduct regular risk assessments.
# Secure Coding Practices (Web Developers): Implement secure coding practices for all developed applications.
# Penetration Testing (Security Specialists): Conduct penetration testing annually and after significant changes.
# Vendor Management (Procurement Manager/Security Manager): Ensure third-party vendors comply with PCI DSS requirements.
# Two-factor Authentication (System Administrators): Implement two-factor authentication for remote access for administratrs and staff. Two-factor authentication is not required for a end user (website customer).
# Application Firewall (System Administrators): Deploy web application firewalls (WAF).
# Incident Response Plan (Security Manager): Develop and test an incident response plan.
# Data Encryption Policies (System Administrators/Web Developers): Develop and maintain data encryption policies.
# Security Policies Documentation (Security Manager): Document all security policies and operational procedures.
# Physical Security Enhancements (Security Manager): Improve physical security measures for server and data access points.
# Authentication for System Components (System Administrators): Strengthen user authentication mechanisms for system components.
# Protection Against Social Engineering (Security Manager): Implement measures to protect against phishing and social engineering attacks.
# Security Scans and Audits (System Administrator/Security Specialist): Perform a security scans and audits. Provide a report to Berean Christian Church the PCI complinece report.
*2FA/MFA only for Administrators and Staff required.*
PCI DSS v4.0, like its predecessors, focuses on securing cardholder data and ensuring the secure processing, transmission, and storage of such data. The standard mandates the use of Multi-Factor Authentication (MFA) primarily for personnel accessing the cardholder data environment (CDE) or sensitive systems, emphasizing an added layer of security beyond just a username and password.
 
For regular users or customers of a website that accepts payments, PCI DSS v4.0 *does not specifically mandate* the use of Two-Factor Authentication (2FA) or Multi-Factor Authentication (MFA) for their interactions, such as making a payment or accessing their account information. The requirements around MFA are more focused on the administrative, access control side to secure the systems and environments handling cardholder data from unauthorized access, particularly for those with the capability to impact the security of the CDE.
*Password Lengh update only for Administrators and Staff required.*
As of my last update in April 2023, *PCI DSS v4.0 does not specifically mandate an increase in password length from 8 to 12 characters for regular users (e.g., customers) of websites that accept payments*. The detailed requirements around password strength primarily focus on those individuals who have access to the cardholder data environment (CDE) or are otherwise involved in the management, processing, or transmission of cardholder data.
 
PCI DSS v4.0 continues to emphasize strong access control measures, including the use of robust authentication methods to secure system components within the CDE. For users within the scope of the CDE, including administrators and anyone with access to sensitive areas, the guidance has indeed become more stringent over time, advocating for stronger authentication methods, which may include more complex password requirements, among other controls.
 
h3. *Pre-Upgrade Backup and Server Transition Strategy*
The Verixity development team will initiate the PCI compliance upgrade process by creating a comprehensive backup of the entire system. This precaution ensures that all data and configurations are securely stored before any compliance-related modifications commence. Additionally, a dedicated backup server is prepared to take over as the primary server once the PCI compliance enhancements have been fully implemented on the current primary server. Presently, this primary server hosts the four websites for Berean Christian Church, underlining the importance of a seamless transition to maintain uninterrupted services during and after the upgrade.
h3. *Project Timeline and Collaboration*
Verixity is scheduled to commence work on April 1, 2024, with an anticipated completion timeframe of two business weeks for the task list outlined above. The Verixity development team will maintain close coordination with the administrative staff at Berean Christian Church throughout this period to guarantee the project's timely delivery.
Backlog Unresolved --
  • CreatedApril 16, 2024 8:34 AM
  • UpdatedMay 15, 2024 10:35 AM
CHURCH-15 Remove an additional block from the Cart
  • Development
Under the radio buttons Partner/ Player and before PROCEED t...
Under the radio buttons Partner/ Player and before PROCEED to Payment button to place a text field , which will be storing information of the name of the other person. 
*Partner's/ Players' Full Name*
 
!Screenshot 2023-11-22 at 16.40.10.png|width=492,height=312!
 
 
------///// OLD
1) Once user already chose an event and filling up the form, we would need to remove the block at the bottom of the page with an additional event.
 
2) The price line in the shopping cart for an additional player is not needed. Only one player at a time can register and pay for the one or two day Pickleball event.
 
He or she can designate a partner. However, the partner will have to register and pay separately.
 
 
Done Done --
  • CreatedNovember 22, 2023 6:30 AM
  • UpdatedFebruary 19, 2024 9:52 PM
CHURCH-14 Additional event registration “Pickleball”
  • Development
{color:#0747a6}*Мероприятие  “Pickleball” будет проходить 2 ...
*Мероприятие  “Pickleball” будет проходить 2 дня (декабрь 2 и 3). Стоимость регистрации - $50 за один день, а если за 2 дня - то $75.*
(A person can register for one date/event for $50.  If the person would like to register for the two days then it will cost $75. )
 
 
 
Add an additional event registration called *“Pickleball”*
 
The registration information that they are seeking to *capture* are:
Participant
Full Name________________________
Address__________________________
Email____________________________
Cell Phone ________________________
Age__________
Saturday, DECEMBER 2, Gender Doubles
* Novice/Beginners:              2.5 (все эти цифры означают уровень участника - The numbers indicate “skill level”)
* Intermediate                     3.0
* Intermediate                       3.5
* Advance:                              4.0
Event:
Sunday, DECEMBER 3, Mixed Doubles
* Novice/Beginners:              2.5
* Intermediate                     3.0
* Intermediate                     3.5
* Advance:                              4.0
 
Текстовое поле Name of Partner/ Player _____________________, где регистрирующийся юзверг может указать имя своего партнера. Партнер должен будет так же заплатить за мероприятие (цена такая же как для регистранта).
Have League choose my Partner (if a player is available)
Yes_      ___No____
 
 
The cost of the event is:
1 Event $50.00 Per Player
2 Event additional $25 per player
Done Done --
  • CreatedNovember 14, 2023 8:41 AM
  • UpdatedNovember 30, 2023 6:32 PM
CHURCH-13 Issue with emails
  • WP
Access credentials: [https://kb.verixity.com/x/TwCV]   ...
Access credentials:
https://kb.verixity.com/x/TwCV
 
 
 
|Server/smart host|smtp.office365.com|
|Port|Port 587 (recommended) or port 25|
|TLS/StartTLS|Enabled|
|Username/email address and password|Enter the sign in credentials of the hosted mailbox being used|
 
Here are the credentials for the email box that we need to use for Berean FLC.
 
flcfinance@bereanchristianchurch.org
P/W: !Finance@2023!
Office 365 email client
SMTP Port 587
TLS enabled
 
!image001-1.png|thumbnail!  
 
 
 
 
-----///// OLD
 
Perhaps BCDC and Anthony’s emails are being blocked by their email server because it knows that, from its side, “BCDCfinance@bereanchristianchurch.org via echurchgive.net” did not originate from itself.  Also, the extension echurchgive.net doman is no longer in our portfolio.  Could this be possibly the case for the emails not getting through  and if they do seldomley  get through they are directed to “Junk Email”?
 
<<  bcdcfinance=bereanchristianchurch.org@echurchgive.net  >>
 
Is there another approach we can take in sending the email from something other than “@echurchgive.net
 
(Нужно проверить почему имеется проблема с имейлами BCDCfinance@bereanchristianchurch.org и Anthony.Sewell
а также понять почему они идут через echurchgive.net)
Done Done --
  • CreatedOctober 22, 2023 8:55 PM
  • UpdatedNovember 30, 2023 6:40 PM
CHURCH-12 Testing
  • Testing
Testing
Done Done --
  • CreatedSeptember 25, 2023 11:04 AM
  • UpdatedFebruary 8, 2024 12:14 AM
CHURCH-11 New task
  • Testing
не приходят имейл при сбросе пароля   Max Volkov @m.volk...
не приходят имейл при сбросе пароля
 
Max Volkov @m.volkov12:34 PM
когда я меняю в ручную в админке- имейл приходит о том что типо поменяли для тебя пароль
 
Done Done --
  • CreatedSeptember 25, 2023 10:44 AM
  • UpdatedFebruary 8, 2024 12:08 AM
CHURCH-10 IpPay documentation - *From:* Seabhac McGinty *Sent:* Friday, March 13, 2020 4:33...
*From:* Seabhac McGinty
*Sent:* Friday, March 13, 2020 4:33 PM
*To:* oneil@fosterinnovations.net; IPpay Support <support@ippay.com>
*Subject:* IPpay API documentation
 
Oneil –
 
Good afternoon!
 
Attached are copies of the current API documentation for our gateway. If at any point you decide to accept ACH/eCheck processing, let us know and we’ll get those documents over to you.
 
Please let is know if you have any questions.
 
Thank you and have a great weekend!
 
~Falcon
 
|*Seabhac "Falcon" McGinty*
Sr. Technical Support Specialist|
| |
|2001 Broadway \| Ste. 600 \| Riviera Beach, FL 33404
tel: (561) 513-8778|
|*website* *\|* *email* *\|* *map* *\|*|
|_One of the ConVergence Technologies Family of Companies_|
|*Confidentiality Note:* This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.|
Done Done --
  • CreatedSeptember 20, 2023 9:39 AM
  • UpdatedNovember 30, 2023 6:38 PM
CHURCH-9 Additional tasks
  • Development
# Instead of Boy and Girls as the gender selection can you m...
# Instead of Boy and Girls as the gender selection can you make the options “Male” and “Female.” *(вместо Boy and Girls  в селекторе формы поставить “Male” and “Female.” )
*++
# Can you make the “Waiver” pop up box larger for readability purposes. (*сделать поп-ап с “Waiver”  больше по размерам, так как плохо читается юзвергами)*
++++
# Attached is the new graphics for the 2023 basketball flyer and the new waver form which will replace the current outdated ones. *(прикреплена новая графика для 2023 basketball flyer и новая waver form - их нужно заменить, так как прошлые уже устарели)*
++++
# On the receipt, please separate the registered players with a blank line. Thus, when a second and third player are added, a blank line will be separate each additional player on the receipt. *(в чеке receipt всех игроков нужно отделить друг от друга, сделать больше пространства между каждым из них. Таким образом, когда второй и третий игроки добавлены, белое пространство их должно отделять).
*
# Change the button title from “Register for Event” to “Proceed to Payment” and have this button go directly into the “Shopping Cart.”  We seek to stream line the user interaction. *(поменять название кнопки с “Register for Event” на “Proceed to Payment”, при нажатии на которую она должна вести сразу же в “Shopping Cart.”)*
#  The sender of the receipt email says Char Jenning <char.jennings=bereanchristianchurch.org@echurchgive.net> she no longer works at the church!!! Change the sender of the email to BCDCfinance@bereanchristianchurch.org
*(убрать имейл адрес bereanchristianchurch.org@echurchgive.net и заменить на BCDCfinance@bereanchristianchurch.org )*
 
# Can you please change the default email address from felecia.anthony@bereanchristianchurch.org  to BCDCfinance@bereanchristianchurch.org . This is one of the two admin email addresses that receipts are sent to.
*(поменять дефолтный имейл адрес с  felecia.anthony@bereanchristianchurch.org  на BCDCfinance@bereanchristianchurch.org )*
++++
# Lastly, delete all old transactions including testing transactions from the data table. This will prepare us to go live with valid/good data. *(удалить все трансакции, включая тестовые).*
 
Done Done --
  • CreatedSeptember 14, 2023 2:56 PM
  • UpdatedOctober 22, 2023 8:31 PM
CHURCH-8 Gender, Waiver, Transaction ID
  • WP
1) Waiver link to highlight in +{color:#de350b}red color and...
1) Waiver link to highlight in +red color and underline it.
+Waiver to be opened in a pop-up (not in a new tab). By placing a ✅  tick mark or by clicking on the Agreement of Waiver, a pop-up with the Waiver content to be shown. A user read all the content and need to click on the “I agree to the terms” button which would return focus to the main form.
!image-2023-09-05-13-03-58-567.png!  
+
+
2) To cross-check Transaction ID after order is placed/ paid.
It should say  “Paid” instead of the transaction details.
Access credentials to the client's real account:
Login: admin
Password: VNjkdnjfk&09395409435KNVFLKSDf

 
!image-2023-09-05-12-24-01-713.png|width=751,height=387!
 
3) Change location of Sex/ Gender - each form needs to include Sex.
 
!image-2023-09-05-13-09-07-384.png|width=727,height=489!
Done Done --
  • CreatedSeptember 5, 2023 11:25 AM
  • UpdatedSeptember 6, 2023 12:04 PM
CHURCH-7 Upgrade 4 websites
  • Development
Upgrade WP websites: 1) [https://bflc.3pm.services/wp-adm...
Upgrade WP websites:
1) https://bflc.3pm.services/wp-admin/
 
Login: max
Password: %bNB&4BqpzD963X54KmR8qsY
2) https://bccgwinett.3pm.services/wp-admin/
 
Login: max
Password: 3oKjRQI77u7bvrkj7O!zCgX^
 
3) https://bccstonemountain.3pm.services/wp-admin/
 
Login: max
Password: J0v2l$vs#!X2jd(12ezkal18
 
4) https://bcchenrycounty.3pm.services/wp-admin/
 
Login: max
Password: D!NB0p)mDYBuv&R)7$n*6tLR
---
 
Done Done --
  • CreatedAugust 30, 2023 1:33 PM
  • UpdatedSeptember 6, 2023 12:04 PM
CHURCH-6 dynamic form is needed for each registrant
  • Request_to_team
When you try to register 2 children, the uniform size inform...
When you try to register 2 children, the uniform size information is only collected for the first player. We need a dynamic form that will request that information for each registrant.
Done Done --
  • CreatedAugust 29, 2023 1:12 PM
  • UpdatedAugust 30, 2023 9:13 AM
CHURCH-5 dynamic form is needed for each registrant 1) When you try to register 2nd child, the uniform size info...
1) When you try to register 2nd child, the uniform size information is only collected for the first player. We need a dynamic form that will request that information for each registrant. Top, Bottom and Date of Birth is needed for each child (динамическая форма должна быть показана при регистрации каждого дополнительного ребенка).
2) Что-то можно сделать с processing time после проведения оплаты, чтобы сократить время ожидания? может какой-то поп-ап вывести с надписью Processing... Please wait
The processing time for the transaction is very long!!! A normal user will try to press the back button or close the browser in order to attempt again.++++
3) Вместо актуального terminal ID поставить/ заменить на “Approved”
IPPay does not want us to display the Terminal ID.  This can give a hacker vital information.  In place of the actual terminal ID just say “Approved”
4) Юзверг, который заплатил, должен получить чек по имейлу. Клиент пишет, что не получил имейла.
Lastly, I did not receive an email for the transaction at oneil@fosterinnovagtions.net;  A copy was sent to the flc.kiosk@gmail.com. Which show a copy sent to Anthony and Felecia.  Again, as the paying person, I did not receive a receipt.
Done Done --
  • CreatedAugust 29, 2023 1:11 PM
  • UpdatedFebruary 8, 2024 12:14 AM
CHURCH-4 Correction after client review 1) после проведения оплаты и транзакции не пришел имейл с че...
1) после проведения оплаты и транзакции не пришел имейл с чеком (receipt email).
Receipt emails are going to three different addresses: (имейл с чеком должен отправляться по 3м адресам + иметь пдф файл waiver)
flc.kiosk@mail.com
Anthony.sewell@bereanchristianchurch.org 
bcdcfinance@bereanchristianchurch.org
as well as the paying user who also receives a copy of the  waiver.
 
 
!image-2023-08-25-11-24-26-431.png|width=568,height=319!
!image-2023-08-25-11-24-39-596.png|width=567,height=318!
 
2) To place in the Admin panel WooComerce tab  the last 4 digits of the  users credit card number 
!image001.png|width=364,height=204,thumbnail!
Done Done --
  • CreatedAugust 25, 2023 10:27 AM
  • UpdatedAugust 28, 2023 11:38 AM
CHURCH-3 FLC Site Test
  • Development
Access Credentials: https://kb.verixity.com/x/TwCV   ...
Access Credentials:
https://kb.verixity.com/x/TwCV
 
 
---
 
Мы получили новый запрос касательно христианских сайтов, в частности сайта https://bflc.3pm.services/. Необходимо внести следующие обновления:
# При успешной транзакции должен приходить email.
# В ресите, который получает клиент, должны отображаться последние четыре цифры кредитной карты.
# Необходима форма-договор (вейвер форм): в качестве родителя я должен иметь возможность ее заполнить и передать в эту церковь.
# Уведомления на указанные два email-адреса клиентов следует отправлять только после получения полной оплаты.
# Требуется добавить функцию предоставления скидки: если регистрируется более одного ребенка, предоставляется скидка в 25 долларов. Необходимо проверить, был ли такой функционал ранее и активировать его; если нет – реализовать.
# Нужно добавить возможность выбора получения агрегированного вейвера: при активации этой опции, я должен получить его в мою корзину покупок.
Прошу учесть все указанные моменты при доработке сайта.
 
-------------------
 
Good morning Max and team,
I just performed a $2.75 realtime sample transaction for BFLC Youth Basketball registration.  These are my findings:
# I did not receive an email receipt for the transaction
# On the receipt, the last 4 digits of the credit card number used is supposed to be displayed on-screen and printed.
# The waiver form was not emailed to me.
 
These are the item(s) that need to be added to the existing process:
# Only on payment in full should the registration and payment information be sent to the following address (Anthony.sewell@bereanchristianchurch.org and bcdcfinance@bereanchristianchurch.org)
# A price discount schedule needs to be added that allow for the second and so forth registrant to receive a $25 discount.  For instance, first child $150, second child $125, third child $125; thus a shopping cart automatic total of $400.
# We need to have a required check box “Agreement of Waiver” that the user must check inorder to process the transaction.  The waiver check box should be placed above the “Registration” button for each registrant. Include the URL to allow the user to view the waiver form and return to the transaction.  Upon agreeing to the waiver (by checking the box) the item will be added to the shopping cart.
Done Done --
  • CreatedAugust 25, 2023 9:20 AM
  • UpdatedAugust 28, 2023 12:17 PM
CHURCH-2 All PM tasks
All PM tasks
Selected for Development Unresolved --
  • CreatedAugust 21, 2023 11:04 AM
  • UpdatedJuly 27, 2025 12:04 PM
CHURCH-1 FLC Site review and requirements - (fixes next week)
  • Development
Мы получили новый запрос касательно христианских сайтов, в ч...
Мы получили новый запрос касательно христианских сайтов, в частности сайта https://bflc.3pm.services/. Необходимо внести следующие обновления:
# При успешной транзакции должен приходить email.
# В ресите, который получает клиент, должны отображаться последние четыре цифры кредитной карты.
# Необходима форма-договор (вейвер форм): в качестве родителя я должен иметь возможность ее заполнить и передать в эту церковь.
# Уведомления на указанные два email-адреса клиентов следует отправлять только после получения полной оплаты.
# Требуется добавить функцию предоставления скидки: если регистрируется более одного ребенка, предоставляется скидка в 25 долларов. Необходимо проверить, был ли такой функционал ранее и активировать его; если нет – реализовать.
# Нужно добавить возможность выбора получения агрегированного вейвера: при активации этой опции, я должен получить его в мою корзину покупок.
Прошу учесть все указанные моменты при доработке сайта.
 
-------------------
 
Good morning Max and team,
I just performed a $2.75 realtime sample transaction for BFLC Youth Basketball registration.  These are my findings:
# I did not receive an email receipt for the transaction
# On the receipt, the last 4 digits of the credit card number used is supposed to be displayed on-screen and printed.
# The waiver form was not emailed to me.
 
These are the item(s) that need to be added to the existing process:
# Only on payment in full should the registration and payment information be sent to the following address (Anthony.sewell@bereanchristianchurch.org and bcdcfinance@bereanchristianchurch.org)
# A price discount schedule needs to be added that allow for the second and so forth registrant to receive a $25 discount.  For instance, first child $150, second child $125, third child $125; thus a shopping cart automatic total of $400.
# We need to have a required check box “Agreement of Waiver” that the user must check inorder to process the transaction.  The waiver check box should be placed above the “Registration” button for each registrant. Include the URL to allow the user to view the waiver form and return to the transaction.  Upon agreeing to the waiver (by checking the box) the item will be added to the shopping cart.
Done Done --
  • CreatedAugust 18, 2023 9:57 AM
  • UpdatedAugust 28, 2023 12:12 PM
- Summary Progress View more

Summary Progress

Key Subject Labels Request Attachments Status Dates
- Tasks Assign to Client View more

Tasks Assign to Client

Key Subject Request Attachments Priority Comments Status Resolution Current Environment Labels Dates
1 Tasks Assigned to Team View more

Tasks Assigned to Team

Key Subject Request Attachments Priority Comments Status Resolution Current Environment Labels Dates
CHURCH-6 dynamic form is needed for each registrant When you try to register 2 children, the uniform size inform...
When you try to register 2 children, the uniform size information is only collected for the first player. We need a dynamic form that will request that information for each registrant.
Medium Done Done --
  • Request_to_team
  • CreatedAugust 29, 2023 1:12 PM
  • UpdatedAugust 30, 2023 9:13 AM

Access Credentials

Nothing found.

For addition information, please contact customer support.

Feedback