Search
Close
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Notifications
Clear all

[Solved] Notice: Undefined variable: topicURL

8 Posts
4 Users
1 Reactions
7,225 Views
Posts: 7
Customer
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@maccast)
Member
Joined: 8 years ago
[#2233]

I'm getting the following error in the "Blog to Forum Cross Posting" box when editing a post:

Notice: Undefined variable: topicURL in /var/www/bbm/mydomain.comhtdocs/wp-content/plugins/wpforo-cross-posting/wpForoCrossPosting.php on line 102 

Screen Shot 2018 04 11 at 9.19.39 PM

In reviewing the code it looks like the bug is because this post existed prior to the installation of WpForo and so when it calls `get_meta` to set `$topicID` it gets set to blank. Then the `if($topicID)` on line 101 fails and `$topicURL` never gets set.

A possible fix would be to change the `if ($topicID)` statement on line 102 to `if ( !empty($topicID) )`


7 Replies
Astghik
Posts: 6645
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@astgh)
Illustrious Member
Joined: 8 years ago

Hi maccast,

Thank you for letting us know,  we'll check and back to you ASAP.


Reply
Posts: 60
Customer
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@studio500)
Member
Joined: 9 years ago

I have the exact same issue - just for info


Reply
1 Reply
Customer
(@studio500)
Joined: 9 years ago

Member
Posts: 60
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

Is there an update on this please?


Reply
Posts: 4245
 Tom
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tomson)
Famed Member
Joined: 11 years ago

Yes, this is fixed.


Reply
1 Reply
Customer
(@studio500)
Joined: 9 years ago

Member
Posts: 60
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian

Thank you,

Has the fix been rolled out yet because I'm still seeing the same error on my post and page editing pages

foro2

.

Notice: Undefined variable: topicURL in /home/xxxxxx/public_html/wp-content/plugins/wpforo-cross-posting/wpForoCrossPosting.php on line 102


Reply
Posts: 4245
 Tom
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tomson)
Famed Member
Joined: 11 years ago

Ok, please update to the latest 1.1.1 version and check it again.


Reply
Page 1 / 2
Share:
Scroll to top