Recent posts - Page 5 Recent posts - Page 5
 

News:

CPG Release 1.6.27
change DB IP storage fields to accommodate IPv6 addresses
remove use of E_STRICT (PHP 8.4 deprecated)
update README to reflect new website
align code with new .com CPG website
correct deprecation in captcha

Main Menu

Recent posts

#41
cpg1.6 miscellaneous / Re: Error messages
Last post by ron4mac - January 01, 2026, 09:30:52 PM
When looking at the issue minicms is having with PHP8.3, I looked at what it takes to switch the editor. I was able to switch to the basic operation of Trix after looking at it for a few hours. I also have experience with embedding CKEditor in one of my own projects. Changing the editor is quite doable ... but is it something worth doing? I'm not sure how relevant CPG is today. There may be only one or two people who have compelling interest in using minicms.
#42
cpg1.6 miscellaneous / Re: Error messages
Last post by phill104 - December 31, 2025, 09:03:12 PM
Just be aware there was a security issue with the editor (FCKeditor) and was never updated. FCKeditor has been discontinued for some time and replaced with CKeditor with a substantial lot of changes since the version shipped with MiniCMS.

Details and links to the repo here - https://en.wikipedia.org/wiki/CKEditor

I am not sure how much work would be needed to replace the editor in the package.
#43
cpg1.6 miscellaneous / Re: Error messages
Last post by sharpo - December 30, 2025, 05:15:54 PM
Thanks for that, glad I mentioned the problem!!

Will look into it later when I have some spare time.
#45
cpg1.6 plugin contributions / Re: MiniCMS for CPG 1.6....
Last post by ron4mac - December 30, 2025, 12:35:05 PM
In the configuration.php file of the plugin, just after the line at the top of the page
if (!defined('IN_COPPERMINE')) die('Not in Coppermine...');insert this new line
global $enabled_languages_array;
#46
cpg1.6 miscellaneous / Re: Coppermine news page fails...
Last post by sharpo - December 30, 2025, 01:19:57 AM
Before I shut down for the night, I reloaded the page & it immediately told me there was an update.

I checked to see what it was - I was running 1.6.26 and the update was to 1.6.27 - so performed the update & checked to make sure no errors.

So for me, problem sorted now.
#47
cpg1.6 miscellaneous / Re: Error messages
Last post by sharpo - December 29, 2025, 10:29:31 PM
That's interesting!!

You've always been very helpful in the past when I've had problems, if you do have any spare time and can easily fix it, it could be useful.

Keep me posted!!

Thanks, sharpo.
#48
cpg1.6 plugin contributions / Re: MiniCMS for CPG 1.6....
Last post by findingcolors - December 29, 2025, 10:15:17 PM
Quote from: mustachio on August 09, 2024, 08:07:26 AMHi, I'm running cpg1.6.26 and I'm getting this error when I go to install the plugin:

`Fatal error: Uncaught TypeError: in_array(): Argument #2 ($haystack) must be of type array, null given in /home/vol2_8/epizy.com/epiz_34139048/htdocs/plugins/minicms/configuration.php:38 Stack trace: #0 /home/vol2_8/epizy.com/epiz_34139048/htdocs/plugins/minicms/configuration.php(38): in_array('english', NULL) #1 /home/vol2_8/epizy.com/epiz_34139048/htdocs/pluginmgr.php(329): include('/home/vol2_8/ep...') #2 /home/vol2_8/epizy.com/epiz_34139048/htdocs/pluginmgr.php(725): display_plugin_list() #3 {main} thrown in /home/vol2_8/epizy.com/epiz_34139048/htdocs/plugins/minicms/configuration.php on line 38`

Is there a simple change I can make on my side to fix this? I was able to find the line it's talking about, but I don't know enough about PHP to actually fix it. Thank you!
Still having this issue as of 12/29/2025
#49
cpg1.6 miscellaneous / Re: Error messages
Last post by ron4mac - December 29, 2025, 05:06:52 PM
If it's of any importance, there a simple fix that will allow minicms to function with php8.3 ... although I have not fully tested it beyond basics.
#50
cpg1.6 upload / Re: Upload Image Size Bugs
Last post by 406man - December 29, 2025, 04:58:10 PM
Quote from: ron4mac on September 14, 2025, 10:09:25 PMPlease fork a copy of CPG 1.6.x at GitHub. Make the changes to your copy and then submit a pull request.
I've done this and also included the fixes for two other bugs previously reported in this forum. It's the first time I've used git and github and hopefully all is in order. If there are any errors or omissions let me know. Thanks.