0

The Content:Path is used to create a Read More button, that redirects the user to another page from View.

It had a previous Rewrite Result of:

<a href="[path]" class="readmore"> Read More </a>

I want the change the string to See More, so I thought it would be a easy change. Boy was I wrong.

No matter what I input into the Rewrite Results output field, it will always default to display Read More (with it's class and href). I can write gibberish, and the View wouldn't show what I wrote and default back to Read More (though preview does display accordingly).

The only time I can get it to display different is when I leave the field empty, or disable Rewrite Result functionality, which it defaults to the content path.

Can anyone explain this weird behaviour? I've done some checks if there's a hook influencing the view, but couldn't find anything.

  • Do you have other options enabled that might affect this, like the Output this field as a link option? – prkos Sep 1 '18 at 16:51
  • Hi @prkos, where should I be looking for this option? – solaris Sep 2 '18 at 21:31
  • It's just below the Override output area, in the same collapsible fieldset "Rewrite results". Can you explain about the bit that preview displays accordingly? It displays changes? But not when visiting the page? Then it may be some hook in your default theme. – prkos Sep 2 '18 at 21:46
  • You know when you edit a view, below the options is a preview of what would be displayed (without css applied). In that preview, it correctly shows See More. But when I save the changes of the View and view the actual page, it still displays Read More. I do not have that option enabled. Or anything I could tell is important. – solaris Sep 2 '18 at 22:25
  • The Views Preview is using the admin theme, that is why it seems to you that "there is no CSS applied". There is CSS, only from the admin theme, and not from your default theme. You probably have something in your default theme affecting this. To test, apply a different theme to your site, usualy the original Garland is used to test theme bugs. If it works in Garland, then you know it's your theme causing the problem. – prkos Sep 2 '18 at 22:46

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.