Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8656567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 12, 20262026-06-12T15:18:27+00:00 2026-06-12T15:18:27+00:00

after updating twig to > than 1.7 code <a href={{ url(‘article’, { ‘articleId’:article.id })

  • 0

after updating twig to > than 1.7

code <a href="{{ url('article', { 'articleId':article.id }) }}"> causes:

Twig_Error_Runtime: An exception has been thrown during the compilation of a template ("Catchable Fatal Error: Argument 2 passed to Twig_Environment::addFunction() must implement interface Twig_FunctionInterface, instance of Twig_Filter_Function given

with 1.7 – everything is ok

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-12T15:18:28+00:00Added an answer on June 12, 2026 at 3:18 pm

    You have to use path(...) instead of url(...).
    Arguments are the same.

    I suppose that from 1.7 to > 1.7 this function became obsolete and was substituted with new one

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

After updating to php 5.3 one of our systems has developed an interesting bug.
After updating to Parsec 3.1 from 2.x, code using many1, such as word =
After updating to Wordpress 3.2.1 my photo gallery plugin, Photo Galleria , has now
After updating or creating a record I use url helper to redirect to the
After updating my mongo client to 2.0.2 the error has changed significantly. New issue
After updating to XCode 4.3, all my archives built using XCode 4.2 are gone.
After updating my ADT plugin to version 17 I'm getting a warning massage saying
after updating to R 2.15, the alpha channel in ggplot does not seem to
After updating to WHM/cPanel 11.30.0, PHPMailer mails are now being rejected by exim. This
UPDATE: After updating to stylus 0.7.4 and express 2.3.12 I can no longer reproduce

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.