Check your right on the recording of the folder  ./uploads. Change the rights via CHMOD 775 or CHMOD 777

552

(25 replies, posted in Problem Solving / Help & Support)

This line appears in the code core/com/allow_active_news.php and core/com/allow_comments.php. It begins with <div class="fb-comments" data-href= just add after data-num-posts a string data-colorscheme="dark".

553

(1 replies, posted in Problem Solving / Help & Support)

This kind of error can happen if there is no permission on the server. Also give the text of the error or a screenshot that is shown while update. You can use our bug tracker https://cutephp.com/cutenews/bugtracker.php

554

(1 replies, posted in Problem Solving / Help & Support)

On Github (the latest version) there is a solution of this problem with migration from Cutenews-UTF-8 to Cutenews 1.5.2  https://github.com/CuteNews/cute-news-repo/...hive/master.zip

This will be fixed in the next version.

556

(9 replies, posted in News)

Try to copy all the files from data to cdata to restore the settings.

There are corrections of this bug on github. Download zip file and install new files  https://github.com/CuteNews/cute-news-repo/...hive/master.zip

That made rss to stop work completely & made åäö stop working on the main page.

But I think I know where the problem is. It's the title. If you look here http://nhlkollen.se/ny/admin/rss.php?category=1 it's only missing åäö in the title. And when I did this solution you sent me, åäö stopped working in the titles on the site as well. I've no idea how this problem came to be tho!


You should have replaced the sequence  " ...... (exact chars in zip file) ..." with the symbols from the zip file we had sent you before, as the forum decodes these symbols back into characters.
So, please send functions.inc.php file to support@cutephp.com, and we'll take the necessary changes; or, alternatively, attach the file on the forum.

For this try to change in  ./inc/functions.inc.php the line

function replace_news($way, $sourse, $replce_n_to_br=TRUE, $use_html=TRUE){
    global $HTML_SPECIAL_CHARS, $config_allow_html_in_news, $config_allow_html_in_comments, $config_http_script_dir, $config_smilies;


to

function replace_news($way, $sourse, $replce_n_to_br=TRUE, $use_html=TRUE){
    global $HTML_SPECIAL_CHARS, $config_allow_html_in_news, $config_allow_html_in_comments, $config_http_script_dir, $config_smilies, $template;


where

$sourse  = preg_replace($find,$replace,$sourse);
           foreach ( $HTML_SPECIAL_CHARS as $key=>$value  ){
                     $sourse = str_replace($key,$value,$sourse);
           }


change to

$sourse  = preg_replace($find,$replace,$sourse);
           if ($template != 'rss') { foreach ( $HTML_SPECIAL_CHARS as $key=>$value  ){
                     $sourse = str_replace($key,$value,$sourse);
           } }
           else { $HTML_SPECIAL_CHARSRSS = Array
           (
              ...... (exact chars in zip file) ...
           );
               $sourse = str_replace(array_values($HTML_SPECIAL_CHARSRSS), array_keys($HTML_SPECIAL_CHARSRSS), $sourse);
           }


in same file

Hi! The åäö stopped working a long time ago: http://nhlkollen.se/ny/admin/rss.php?category=1
I remember saving or changing something/some file, and haven't been able to fix it since that... I'm rebuilding the site with 1.5.2 but until that, I would like to fix this problem... Either by going to the root of the problem or by some workaround fix.


Specially in case of correction of "åäö" there is a plugin that corrects the bug in RSS. The php file in zip file should be got to  ./cdata/plugins/

html_entity_rss.zip

This error appears because of mismatch of the version PHP. In the file ./core/init.php in the line 80 change
set_error_handler("user_error_handler", E_ALL);
to
set_error_handler("user_error_handler");

562

(10 replies, posted in Problem Solving / Help & Support)

The changed in 1.5.2 in addnews.php / editnews.php concerned only the function preview. If addition or editing of news appear because of this so try in addnews.php (version 1.5.2) add under the line
    // ********************************************************************************
    // Do add News to news.txt
    // ********************************************************************************

the following line

    $preview = (REQ('preview') == 'preview') ? 'preview' : false;

In editnews.php after the line

    // Detect
    if (REQ('saved','GETPOST') == 'yes') $saved_yes = 1;
    elseif (REQ('saved','GETPOST') == 'add') $saved_new = 1;

the line

    $preview = (REQ('preview') == 'preview') ? 'preview' : false;

If the problem disappears so it was caused by wrong variable transmission. If no, you can send us the file from ./cdata/log/error_dump.log. We'll try to solve the problem as soon as possible.

563

(10 replies, posted in Problem Solving / Help & Support)

It can be a problem with rights - they can be changed. We recommend the following rights level: for files 664, for folders 775. If it doesn't work try for files 666, for folders 777. The last variant is less dangerous.

564

(10 replies, posted in Problem Solving / Help & Support)

Yes, it's necessary to change from backup (current copy of cdata),i.e. copy all data over the installed cdata.

565

(10 replies, posted in Problem Solving / Help & Support)

Please tell if you had duplicated files cdata before upgrading from 1.5.1 to 1.5.2? If yes change cdata to those in backup. If there are not duplicated files all your data were deleted by installation.
We're sorry for this.

566

(17 replies, posted in Problem Solving / Help & Support)

This functional exists in 1.5.2 but still being tested. Download the latest version from Github (https://github.com/CuteNews/cute-news-repo/archive/master.zip) where we've corrected this bug and install in Options > System configurations >  Custom rewrite = Yes. After this a new menu in Options > URL Rewrite manager will appear.

P.S.
"URL Template name" - the URL that will be shown;
"Use layout" - the original URL where Cutenews will refer to in case of coincidence of template in "URL Template name".

This problem appeared because of a bug. We updated the code that corrected the bug with this commit
https://github.com/CuteNews/cute-news-repo/...c81ce8e5c1befc3

Download the latest version from github  https://github.com/CuteNews/cute-news-repo/...hive/master.zip

Try in Options > System Configurations enter your codepage

"Frontend default codepage" = for example, iso-8859-1
Also,  "Use UTF-8" = No
Don't convert UTF8 symbols to HTML entities (No)

These options return Cutenews 1.5.2 from UTF-8 mode to server coding by default.

In the version 1.5.2 Captcha is locked via Options > News > User Captcha = Yes. It should be noticed that captcha can't be seen for administrator.

570

(17 replies, posted in Problem Solving / Help & Support)

Now we have a manual for creating plug-ins. https://cutephp.com/forum/index.php?showtopic=43289

571

(4 replies, posted in Hacks & Tricks / FAQ)

The idea of plug-ins is that there are the functions hook() that pass the data meanings in the particular places of the original CuteNews code, and these data are handled by plug-ins' filters.

To show how the hooks work we can take for example the code for processing the news template from core.php:

    list($output, $news_arr) = hook('template_replacer_news_before', array($output, $news_arr));


Here the hook is called for the function "template_replacer_news before" the changes of the constructions like {title}, {author} and so on.
Explanations: The array $news_arr is the data with the meanings of the current news, $output is the content of tpl-template, for example the content of Default.tpl.

The called hook has a name "template_replacer_news_before". This name is registered when plug-in initialization and can be used for calling other plug-ins,
i.e. if one plug-in registered the name "template_replacer_news_before" and another one did the same then the function of the first plug-in will be called primarily.

Let's create the first plug-in.  Name it my_plugin.php and place in ./cdata/plugins directory.

Here are the the plug-in snippet:

<?php 

    /*
        Connect the hook "template_replacer_news_before" with the function 'my_plugin_trnewsb'.
        It means that while calling the hook ('template_replacer_news_before', $args) the function my_plugin_trnewsb() will be called that will have the parameter $data.
    */       

    add_hook('template_replacer_news_before', 'my_plugin_trnewsb');

    function my_plugin_trnewsb($data)
    {
        // Here the $data is the array, that's why the hook will return the same array 
        return $data;
    }      

?>


As you can see the mechanism is quite easy. You need to register the hook and write for it the appropriate handler function.

You shouldn't forget to do a 'return' of the data meanings (modified probably) or you can have an incorrect input.
Let's write the new field for templates, for example the field "{show_php_version}"

<?php 

    add_hook('template_replacer_news_before', 'my_plugin_trnewsb');
    function my_plugin_trnewsb($data)
    {
        // Unpack the data from the array
        list($output, $news) = $data;

        // Make a change of {show_php_version} to the meaning PHP_VERSION
        $output = str_replace('{show_php_version}', 'PHP Version is '.PHP_VERSION, $output);            

        // Return the data to the code
        return array($output, $news);
    }   

?>


Now add to the template code, for example to the Full Story the fragment {show_php_version}, then create news and see the PHP version data.

It's easy to make the additional menu in options with the help of plug-ins. Two hooks are responsible for this – "more_options" and "options_additional_actions".
The hook  "more_options" is necessary for adding the links to the section Options, the second one processes the incoming data on ?mod=options&action=options.

An example:
Create the file add_options.php in ./cdata/plugins:

 <?php 

    add_hook('more_options', 'aopt_menu');
    add_hook('options_additional_actions', 'aopt_handler');

    // The parameter $options is passed for this hook, we should add

    function aopt_menu($options)
    {

        $PHP_SELF = PHP_SELF;

        $options[] = array
        (
            'name'              => lang('My plugin!', 'options'),
            'url'               => "$PHP_SELF?mod=options&action=my_more_options",
            'access'            => ACL_LEVEL_ADMIN,
        );

        return $options;
    }

    // The data aren't passed, we should use the global variables
    function aopt_handler()
    {
        // Instead of the straight call $_GET you can use the function REQ
        if (REQ('action','GET') == 'my_more_options')
        msg('info', 'Hello!', lang("It's my FIRST plugin"));

    }

?>


Now in Options there is a new menu 'My plugin!'. While clicking to it we will see the message "It's my FIRST plugin".

Good luck with creating of plug-ins!

572

(1 replies, posted in Problem Solving / Help & Support)

It's corrected in the version 1.5.2.

Теперь Cutenews 1.5.x более не поддерживает прямого включения show_news.php по вопросам безопасности и правилам использования, теперь необходимо создавать "обертки" для новостей, в которых и  будет включен show_news.php. Пришлите пример, откуда идут ссылки на show_news.php, мы постараемся вам помочь.
Cutenews 1.5 doesn't support straight multiple show_news.php on the security issues.  It's necessary to create wrappers for news where show_news.php will be included. Send us an example from where the links are get and we'll try to help.

574

(1 replies, posted in Problem Solving / Help & Support)

Probably you mean the change of time format that is described in the  topic https://cutephp.com/forum/index.php?s=&amp;...st&amp;p=156352

575

(12 replies, posted in Script Feedback and Suggestion)

We appreciate you review a lot. We've corrected the most of the bugs you've noticed in the version Cutenews 1.5.2.