[Bug / Issue] Error information: "0 parserror SyntaxError: Unexpected token s in JSON at position 0"

[m-d-luffy]

hi
I have a problem when you edit topics and replies, the following message appears:

Error
Error information: "0 parserror SyntaxError: Unexpected token s in JSON at position 0"

Continue with the raw technical support of the server was their response:

Checked and activated the debug mode
Also check server errors
There is no recorded error explaining the cause of the problem
The problem is mostly software

use vBulletinVersion 5.4.4 Beta 1
php 7.2

[Mark.B]

5.4.4 is not yet ready for production sites.

Please restore from backup to your previous version, if it is not 5.4.3 you should upgrade to that.

[m-d-luffy]

5.4.4 is not yet ready for production sites.

Please restore from backup to your previous version, if it is not 5.4.3 you should upgrade to that.

The experiment was tested on 5.4.3
The same problem is a stupid program full of problems and complications
The server was checked in all respects without any problem.

[Wayne Luke]

What is the complete JSON string? You can see this by opening the Developer Tools in your Browser and recreating the error. Clicking on the entry in the network tab will show the response from the server.

[m-d-luffy]

What is the complete JSON string? You can see this by opening the Developer Tools in your Browser and recreating the error. Clicking on the entry in the network tab will show the response from the server.

The problem in this code:
Is the old link conversion code:

RedirectMatch 301 t (.) / $ Https://sa-en.anime-toons.tv/showthread.php?t=$1
RedirectMatch 301 f (.) / $ Https://sa-en.anime-toons.tv/forumdisplay.php?f=$1
RedirectMatch 301 u (. *) / $ Https://sa-en.anime-toons.tv/member.php?u=$1

Now the old links are not working are directed to the home page ..
This is my biggest mistake and loss
Is there a way to convert old links ...

I do not know how a company is the size of a company
Ignores customers using legacy releases

[Wayne Luke]

vBulletin 5 will automatically handle 301 redirects from vBulletin 3 and 4 URLS without any changes to the .htaccess file that we provide. It appears that you were using custom URLS through some third-party addon. So you have additional rewrites. Your custom rewrites must occur before this code in the .htaccess that we provide:

    # Main Redirect
    RewriteCond %{REQUEST_URI} !\.(gif|jpg|jpeg|png|css)$
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule ^(.*)$ index.php?routestring=$1 [L,QSA]

If they still don't work, you need to talk to your Server Administrator because customizations of this sort are outside technical support. Which has always been the stated policy. Your server will have to be configured for the extra redirect as well.

[m-d-luffy]

vBulletin 5 will automatically handle 301 redirects from vBulletin 3 and 4 URLS without any changes to the .htaccess file that we provide. It appears that you were using custom URLS through some third-party addon. So you have additional rewrites. Your custom rewrites must occur before this code in the .htaccess that we provide:

# Main Redirect
RewriteCond %{REQUEST_URI} !\.(gif|jpg|jpeg|png|css)$
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?routestring=$1 [L,QSA]

If they still don't work, you need to talk to your Server Administrator because customizations of this sort are outside technical support. Which has always been the stated policy. Your server will have to be configured for the extra redirect as well.

The code was placed in the place you mentioned and did not work
I told the technical support of the server, which is now looking at a solution to the problem ..

======
How to reduce the number of description characters in the slider as shown in the picture :

[m-d-luffy]

up up up

[Mark.B]

up up up

As per the forum rules - Please wait at leas 24 hours before bumping threads. Forum support is not real time, we are not on duty 24/7, and even when we are, we may be working on other customer issues via support tickets.

We will always get to you as quickly as we can.

There is no supported way to limit the number of characters displayed. You can increase the height of the module though.

If you have other questions, please start a separate thread for each, rather than adding new issues to an existing thread, as it quickly becomes confusing and difficult to follow.

[m-d-luffy]

Including technical support always has no solutions.
Solving this problem is:
Delete (<div class="ellipsis">{vb:raw parsedText}</div>) from template (widget_contentslider)

[Mark.B]

Including technical support always has no solutions.
Solving this problem is:
Delete (<div class="ellipsis">{vb:raw parsedText}</div>) from template (widget_contentslider)

We do not provide support for editing templates directly. This is code customisation, and doing it can break future upgrades. We do not and never have provided support for code customisations. We have always had a separate, peer-to-peer support site for that - www.vbulletin.org.

[m-d-luffy]

We do not provide support for editing templates directly. This is code customisation, and doing it can break future upgrades. We do not and never have provided support for code customisations. We have always had a separate, peer-to-peer support site for that - www.vbulletin.org.

And you, what do you offer for the future ..? Fast food . !

www.vbulletin.org.
This site is dead
He does not submit anything new and has been abandoned by his team.
If it is closed it will be better

[In Omnibus]

Being a jerk to support staff might not be the best way of getting your questions answered.

[m-d-luffy]

This topic concerns me and the problem is related to me, why are you available
The more you oppose one customer and stand against their suggestions, the more you are using this method in order to make money from customers to solve their problems. Not far from being paid by vBulletin and internetbrands to praise their poor product
I hope not to be on any topic for me.

[Mark.B]

The question has been answered so I'll close the thread.
As stated, we do not support code modifications, and we never have supported code modifications.
This is not going to change.