91
bjuti
Re: XOOPS 2.5.3 Final Released
  • 2011/10/5 14:13

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Well I slove my problem about not showing custom blocks.

In the upgrade package 245 > 253 system module is broken. I've replaced system module from original install pack and all is ok for now. I'll check other files too.



92
bjuti
Re: XOOPS 2.5.3 Final Released
  • 2011/10/5 7:45

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


@Trabis I did all of that and it didn't resolve the problem.

BUT

When I cloned default templates to custom ones I saw that all ' was written in template like #039; and I've deleted all cloned templates and now is showing default ones.

One more BUT

Now Xoops isn't showing all the blocks. There is one custom html block on the front page and it isn't shown, also left and right columns are images and there is nothing in that blocks.

Debugger say:
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 68
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 69
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 70
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 71
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 71
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 68
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 69
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 70
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 71
Notice: Use of undefined constant _MSC_CLICK_TO_OPEN_IMAGE - assumed '_MSC_CLICK_TO_OPEN_IMAGE' in file /class/textsanitizer/image/image.php line 71

Also there is no background color in css?



93
bjuti
Re: News or XNews module?
  • 2011/10/4 18:10

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Yeah.. but i need to put some projects on hold or use other content modules coz of that. :) Nevermind, I like publisher and fmcontent (still buggy)



94
bjuti
Re: News or XNews module?
  • 2011/10/4 17:00

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Yup, they are not crucial, but they help alot. So, still... we can say chat having rewritten urls is standard in 2011. for nearly every cms, except Xoops (few modules have it, but there is no system support). :)



95
bjuti
Re: XOOPS 2.5.3 Final Released
  • 2011/10/4 16:01

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Is it a bug or i'm just dumb?

I've updated from 2.4.5 to 2.5.3 and my old templates are shown, and that's ok. But I wanna change them and i can't swich to default in system/prefs.

I got this notice:
Error : Smarty error: [in db:publisher_items_new.html line 10]: syntax error: unidentified token '#039;1'' (Smarty_Compiler.class.php, line 1410)

Ok, i cleaned the cache but again, my old template is active not the default. I've tried again, but same thing happened.

Also, I've cloned templates to theme dir, and change it there. Nothing happened.

So, my main goal is to use modules default templates and to change them in module dir and use it like default ones but i had no luck.

What should i do?

Tnx



96
bjuti
Re: News or XNews module?
  • 2011/10/4 15:06

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


News module lacks of url rewrite and it's bad for seo. I can't imagine module without rewrite url and meta description options. Google can't imagine it either



97
bjuti
Re: News or XNews module?
  • 2011/9/28 8:26

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Any progress on this?



98
bjuti
Re: Fmcontent new version : Test and report bugs
  • 2011/9/16 15:14

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


I've found the problem.. modules admin shoudl be in modules classes?!

Ok, now it works but there is one urlrewrite problem.

I can't use the module coz sometimes link is normal eg. for category:
On the front page is:
http://mysite.com/mytopicname/1/myarticle.html

But on myarticle.html topic is (Where is Published in:):
http://mysite.com/topic/2/mytopicname.html and it doesn't work.



99
bjuti
Re: Fmcontent new version : Test and report bugs
  • 2011/9/10 9:14

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Still doesn't work... Fresh Xoops installation 2.5.1a, modulesadmin framework and still notice: '_AM_MODULEADMIN_MISSING'



100
bjuti
Re: Fmcontent new version : Test and report bugs
  • 2011/9/8 6:07

  • bjuti

  • Just can't stay away

  • Posts: 871

  • Since: 2009/1/7 2


Quote:
And when i try to access Admin>Modules>fmContent>Home i get a popup with the remark: "_AM_MODULEADMIN_MISSING".


Same here... Xoops 2.4.5




TopTop
« 1 ... 7 8 9 (10) 11 12 13 ... 64 »



Login

Who's Online

224 user(s) are online (134 user(s) are browsing Support Forums)


Members: 0


Guests: 224


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits