61
aerograf
Re: Problems with Lexicon
  • 2017/12/12 19:34

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


The problem was originally. Specially put unchanged version and checked.
But this problem also pops up on other texts.
This one was given as an example. But what that passes.
If you use htmlSpecialChars, then it naturally stops transcoding the html code and then displays all the text with the formatting tags.
Maybe it works correctly, but in other modules this text skips and saves.

62
aerograf
Re: Problems with Lexicon
  • 2017/12/12 19:41

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


Or refuse to use the apostrophes...
Which is not entirely correct. IMHO

63
Mamba
Re: Problems with Lexicon
  • 2017/12/14 12:02

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


It will be probably the best to replace the backend.
Take a look at this:https://github.com/mambax7/lexikon/tree/feature/backend_test

The two tabs of interest to you are on the right hand-side, Categories and Entries.

With these, you should be able to save the apostrophes.

Please test it and see if it works for you. This is really a "quick & dirty" branch, so don't use it on a production site - this is only for testing as a proof of concept.
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

64
aerograf
Re: Problems with Lexicon
  • 2017/12/14 21:47

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


Yes, it works in these tabs.
How much do I understand that the challenges change completely?
Pretty interesting. The truth is not yet understood more tightly, but I saw a very interesting version of the localization of search and sorting.

65
Mamba
Re: Problems with Lexicon
  • 2017/12/15 2:08

  • Mamba

  • Moderator

  • Posts: 11366

  • Since: 2004/4/23


We need to move to XMF and start utilize all the cool features there, that will make our lives much easier.

Unfortunately in the past, because we had no clear standards, and because XOOPS is so powerful that you can do almost anything in any way you want, we've ended up with a lot of different modules, developed in many different ways.

So now we have to bring all of them together, and standardize by selecting the best ideas and implementing them across all modules. This will improve also the security of the modules, as we'll be re-using code that has been already tested.

I wish, the process would go faster, but at least we have pretty much all modules now using the same Admin GUI, and we're moving more to leverage XMF on the back end.

As you've seen here with Lexikon, the goal is to be able to "swap" the basic CRUD operations, and start consistently using XMF, Criteria, and XoopsPersistableObjectHandlers.

It's a lot of work, but it should be faster than rewriting the backend for each module.
Support XOOPS => DONATE
Use 2.5.10 | Docs | Modules | Bugs

66
aerograf
Re: Problems with Lexicon
  • 2017/12/15 4:38

  • aerograf

  • Quite a regular

  • Posts: 214

  • Since: 2017/1/7 1


I think it's necessary to create a topic and publish recommendations on the development and updating of modules. And also to draw up an approximate list of modules that users use and gradually bring them to standards ...

Login

Who's Online

141 user(s) are online (106 user(s) are browsing Support Forums)


Members: 0


Guests: 141


more...

Donat-O-Meter

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

Latest GitHub Commits