Novice Guru
  • Content Count

  • Joined

  • Last visited

  • Days Won


alexis last won the day on February 22

alexis had the most liked content!

Community Reputation

35 Excellent

About alexis

  • Rank
    Advanced Member
  • Birthday 04/30/1983

Recent Profile Visitors

2,366 profile views
  1. alexis

    Enable post approval as a rule action

    You may try to realize your needs through access to the database using a PHP action in your rule. As far as I know, once post approval is enabled for a topic, at least two important changes inserted into the database: core_content_meta table and forums_topics table. Into the first table such a line is inserted like this: 53 IPS\forums\Topic 95519 core_ItemModeration {"enabled":true,"member":1} And the line in the forums_topics table with topic ID 95519 has the column TOPIC_META_DATA changed from 0 to 1. Also, there should be some specific logs inserted, saying that a moderator enabled post approval in a certain topic. So, you can start with this. I assume it is possible using this way.
  2. alexis

    The CSRF protection key did not match

    on my live test board it has been saved: after that error appears, you need to refresh the page.
  3. alexis

    The CSRF protection key did not match

    In spite of this error, the changes have been saved successfully
  4. alexis

    The CSRF protection key did not match

    You can modify those files directly on your server (just edit the already installed files). On my live test board I did an update through the application page (meaning that first I modified the necessary files in the .tar archive of the Rules application). But on my main board I am going to modify the files on the server, since I got some other small custom modifications on the Rules.
  5. alexis

    CSRF error in IPS 4.5.0

    take a look at this post, this error is easy to fix:
  6. alexis

    The CSRF protection key did not match

    Don't worry guys, luckily this current issue is easy to fix! The only thing we need to do, is to add these lines into all php files in the "modules" folder of any Kevin's application, so it will start working again: /** * @brief Has been CSRF-protected */ public static $csrfProtected = TRUE; The lines should be added inside the first "class" section, lets see it on an picture below: On the left side is a new view, after the changes has been made, on the right side - is it was before (originally). This changes has to be made in the files, because it is a new IPS developers' requirement regarding the security. @Bluto @Dan @liquidfractal @pixeldude @xSeq2 @Zayon
  7. alexis

    The CSRF protection key did not match

    This error appears every time by every of the four main Kevin's applications, when creating any rule, any rule set, any collab, any banks or currency or even a new path alias.
  8. alexis

    4.5.x compatibility

    It is quite possible. It needs more time to test and investigate. Also, there are several applications created by Kevin, so probably not all of them will be completely compatible. Tests are needed.
  9. alexis

    4.5.x compatibility

    There should be an option to manually upload the xml/tar files of plugins and applications: When enabling the Rules, did you notice this kind of error in your ACP? 2S119/1 The CSRF protection key did not match. This may indicate a plugin or theme is out of date. Please contact technical support for more information.
  10. alexis

    4.5.x compatibility

    I am waiting for an update as well...
  11. alexis

    Automatically modify topic's Prefix

    We don't have such an action like "Modify content prefixes" within the Rules actions So the only way to accomplish your needs would be using an "Execute PHP code" as an Action, where you will need to find a right php code, which will correctly set the necessary prefixes... But what a code would it be, I don't know at all
  12. alexis

    Check a member registered date

    I have several recurring scheduled actions on my board. One of them runs everyday with a bulk of 1000 members. And it works fine every night without skipping anyone or being stuck. The second one runs on a weekly basis each Friday afternoon, and it has 500 members in a bulk. And this action often stops running without any reason. So I had to increase the number of members to 1000 too. So both of them run faster now and without stopping. Probably the problems happen because of the high activity level on my board in the day time, so the high server load bothers my action to run successfully until the end. So I can suggest you to try to run your scheduled actions in the deep night or early morning. Another suggestion would be trying to assign some of your rules to another scheduled action, rather then running them under one scheduled action. - divide your rules into two scheduled action and run them one by one. (For example, start one scheduled action at 4.00 AM and the next one at 9.00 AM).
  13. alexis

    Check a member registered date

    Did you try a condition "Member attribute values"? @Zayon
  14. alexis

    Action "Create new event" is broken

    I've checked with the database by command 'SELECT * FROM calendar_events' , and found the events inside! They are just not shown on the community! The difference between them and other, *normal* events, created manually, is the "event_start_date"-column, which is always "0000-00-00 00:00:00" by the Rules created events.
  15. I've tested on several rule events, and unfortunately found out, that the Content Calendar action "Create new event" doesn't work properly. In the rule debug logs it says, that the action is evaluated, and there is even a successful result "content created". But in fact, there are no Events have been created at all When testing, I've added several tags to the Event in the action settings , and the system logs started to show the following error: The error happens when visiting the event author profile or "All activity" page. And there are still no events in Calendar created by this action @Kevin Carwile , could you please confirm, if that's a bug or not, and kindly fix it, if it is a bug? And please do not forget to fix that long-time bug in the Path alias: Thanks,